devm_spi_mem_dirmap_destroy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devm_spi_mem_dirmap_destroy(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual entry for devm_spi_mem_dirmap_destroy(9) β€” yes the name is a mouthful, no we're not changing it, it's iconic in a chaotic way πŸŽ€


✨ NAME ✨

devm_spi_mem_dirmap_destroy β€” Destroy a direct mapping descriptor attached to a device 🌸


✨ SYNOPSIS ✨

void devm_spi_mem_dirmap_destroy (struct device *dev , struct
       spi_mem_dirmap_desc *desc );

✨ ARGUMENTS ✨

  • dev β€” the device that the dirmap desc is attached to 🫢 like, that's its home, that's its whole situation
  • desc β€” the direct mapping descriptor we are destroying. yes. we're ending it. respectfully πŸ’…

✨ DESCRIPTION ✨

so this is the devm_ variant of the spi_mem_dirmap_destroy function. that's the whole vibe. it's the managed, device-tied version of the same thing, and if u want the full lore you gotta see spi_mem_dirmap_destroy for more details ✨ ngl it's literally right there in the name, the devm_ prefix is doing the heavy lifting, love that for it 😭


✨ SEE ALSO ✨

Kernel file ./drivers/spi/spi-mem.c β€” go read it, it's giving main character energy πŸ“–

like?? that's a whole friend group 😭 the create/destroy pair is right there β€” devm_spi_mem_dirmap_create(9) and devm_spi_mem_dirmap_destroy(9), they're literally the it-couple of this page πŸ’–


🧚 quick vibe check: desc is the descriptor u are destroying and dev is the device it's attached to, so keep them straight or the kernel will simply not have a good time πŸ™ˆ

and that's the page!! mwah πŸ’‹ this one lives under ./drivers/spi, blessed by the October 2026 era of the Kernel API Manual β€” devm_spi_mem_dirmap_destroy(9), slay, periodt πŸ‘‘β­

πŸ“¦ where this page comes from