pci_destroy_slot(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pci_destroy_slot(9) β€” Kernel API Manual πŸŽ€

okay so bestie, welcome to the glow-up era of pci_destroy_slot(9) β€” this is the Kernel API Manual page you've been looking for, and honestly? it's short, it's sweet, and it absolutely ate. ✨


🌸 NAME 🌸

pci_destroy_slot β€” decrement refcount for physical PCI slot 🫢

like, that's the whole vibe. you're not deleting anything-deleting anything, you're just... letting the refcount know a friend is leaving the party. πŸ’œ


⭐ SYNOPSIS ⭐

void pci_destroy_slot (struct pci_slot *slot );

no cap, that's the whole signature. void return, one argument, zero drama. πŸ”₯


πŸ¦‹ ARGUMENTS πŸ¦‹

  • slot β€” the struct pci_slot to decrement, i.e. the little guy whose refcount you're about to tick down. that's it. that's the argument. πŸ’…

✨ DESCRIPTION ✨

okay so here's the tea: struct pci_slot is refcounted. which means destroying them is really easy β€” like, suspiciously easy. you literally just call kobject_put on its kobj and then you let the release methods do the rest. 🧚

that's it. that's the whole function. main character energy, minimal lines of code, maximum trust in the release path. the way that it just hands off to kobject_put and vibes? iconic. πŸ‘‘

🫢 gentle reminder that this only works because the struct is refcounted β€” you're not freeing it yourself, you're dropping a reference and letting the release methods handle everything else. the lifecycle stays in its lane, you stay in yours.

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/pci/slot.c β€” go read where the magic actually lives πŸ’–
  • pci_create_slot(9) β€” the other half of the story, the "put it into the world" to this one's "let it go" πŸ¦‹

and that's the page!! mwah πŸ’‹ β€” brought to you by the fine folks over in ./drivers/pci, dated October 2026, and this has been pci_destroy_slot(9). slay, stay refcounted, and don't forget to kobject_put. 🌸✨

πŸ“¦ where this page comes from