module_auxiliary_driver(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… module_auxiliary_driver β€” the Kernel API Manual era πŸŽ€

okay so bestie, welcome to the manual page for module_auxiliary_driver, straight out of the Kernel API Manual ✨ lowkey iconic, highkey useful. Let's get into it 🫢


✨ NAME ✨

module_auxiliary_driver β€” the helper macro that handles registering an auxiliary driver for you πŸ’–


🌸 SYNOPSIS 🌸

module_auxiliary_driver (__auxiliary_driver );

no cap, that's the whole thing. that's the vibe 🌈


πŸ¦‹ ARGUMENTS πŸ¦‹

  • __auxiliary_driver β€” the auxiliary driver struct πŸ’« literally just hand it your driver struct and you're done, slay.

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea β˜• β€” this is the helper macro for auxiliary drivers that do not do anything special in module init/exit. none of that extra credit homework energy, just vibes ✨

the way it eliminates a lot of boilerplate?? honestly obsessed 😭 you don't have to hand-write all that setup noise, the macro ate and left no crumbs πŸ’…

🚨 the rules, bestie, listen up 🚨 each module may only use this macro once. that's it. one time. and calling it replaces module_init and module_exit β€” so don't go doubling up, iykyk πŸ’€

and here's how it looks in the wild:

module_auxiliary_driver(my_drv);

main character macro energy, fr fr πŸ‘‘


πŸŽ€ SEE ALSO πŸŽ€

  • Kernel file ./include/linux/auxiliary_bus.h πŸ“
  • DEVICE_LIFESPAN(9) πŸ•°οΈ
  • struct auxiliary_device(9) 🧚
  • struct auxiliary_driver(9) 🌟

go read those next, they're giving required reading πŸ’–


and that's the page!! πŸ¦‹ brought to you by ./include/linux, dated October 2026, and yes it's module_auxiliary_driver(9) β€” mwah, periodt πŸ’‹πŸŒΈ

πŸ“¦ where this page comes from