device_has_driver_override(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– device_has_driver_override(9) πŸ’–

okay bestie, welcome to the Kernel API Manual entry for device_has_driver_override β€” yes it's a real function, yes it's in section 9, and yes it's lowkey the simplest little icon you'll ever meet. it lives down in ./include/linux and honestly? she's giving one-job-and-she-does-it energy. slay.


✨ NAME ✨

device_has_driver_override β€” check if a driver override has been set. that's it. that's the whole gig. πŸŽ€


🌸 SYNOPSIS 🌸

bool device_has_driver_override (struct device *dev );

literally one argument, one bool back. no cap, that's the entire function signature β€” copy it exactly, don't get creative with it. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device to check. like, the actual struct device * you're curious about. hand her over and she'll tell you what's up. 🫢

⭐ DESCRIPTION ⭐

Returns true if a driver override has been set for this device. πŸ“£

that's the whole description, bestie β€” she's not mysterious, she's not doing a lore drop. true means yeah, an override got set for this device; otherwise you get false. main character energy of a function that knows exactly what it's about. πŸ’€βœ¨


πŸ”₯ SEE ALSO πŸ”₯

okay this is the part where the manpage goes full group-chat-forward energy, because the SEE ALSO list is long. buckle up, we're going through all of it, nobody gets left on read. 🌈

the kernel file in question first:

  • Kernel file ./include/linux/device.h

then the structs and friends:

  • struct subsys_interface(9)
  • struct device_attribute(9)
  • struct dev_ext_attribute(9)

then the whole DEVICE_ATTR family reunion (they all showed up, iconic):

the enums, because we contain multitudes:

  • enum device_link_state(9)
  • enum dl_dev_state(9)
  • enum device_removable(9)
  • enum device_physical_location_panel(9)
  • enum device_physical_location_vertical_position(9)
  • enum device_physical_location_horizontal_position(9)
  • enum struct_device_flags(9)

the structs, the moment you've all been waiting for:

  • struct dev_links_info(9)
  • struct dev_msi_info(9)
  • struct device_physical_location(9)
  • struct device(9)
  • struct device_link(9)

and finally the related-function besties, the ones who actually get the override lore:

not me listing thirty-something SEE ALSO refs and still making it cute 😭 every single one is above, nobody got cut, we ate. πŸ‘‘

and that's the page, bestie! sourced from ./include/linux, dated October 2026, in the Kernel API Manual β€” go check your dev and have the most slay day. πŸ§šπŸ’œπŸ“

πŸ“¦ where this page comes from