bdx_remove(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bdx_remove(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so welcome to bdx_remove(9), straight out of the Kernel API Manual ✨ pull up a chair, we're talking device removal and it's honestly kinda iconic.


🌸 NAME 🌸

bdx_remove β€” the Device Removal Routine, aka the "bestie, pack it up" function 🧳


✨ SYNOPSIS ✨

void bdx_remove (struct pci_dev *pdev );

like, that's the whole signature. no cap. returns void, takes one pointer, done. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pdev β€” the PCI device information struct 🫢 that's the one and only thing you hand over, and it's the device we're saying bye to.

πŸ’– DESCRIPTION πŸ’–

so bdx_remove gets called by the PCI subsystem to slide into the driver's DMs and be like "hey bestie, you gotta release this PCI device." πŸ‘‘ it's a heads-up, not a suggestion.

the way this happens is lowkey two vibes:

  • it could be caused by a Hot-Plug event πŸ”₯ (device showing up or dipping out mid-party), or
  • it could be because the driver is going to be removed from memory πŸ’€ (like, the whole driver, gone, no more).

either way, bdx_remove is your girl. she gets the memo, you release the device, everyone moves on. periodt. 🌈


⭐ SEE ALSO ⭐

Kernel file ./drivers/net/ethernet/tehuti/tehuti.c πŸ“ and honestly the whole friend group of functions, all here, all linked, all (9):

iykyk πŸ’œ


anyway that's the whole page, mwah πŸ’‹ this one lives at ./drivers/net/ethernet/tehuti, it's dated October 2026, and it's filed under bdx_remove(9) β€” go read the others, they're all slaying in their own way πŸ¦‹βœ¨

πŸ“¦ where this page comes from