device_links_driver_cleanup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” this is the page for device_links_driver_cleanup(9), and honestly? it's a little cleanup crew for device links. let's get into it πŸ’…


🌸 NAME

device_links_driver_cleanup β€” update links after driver removal. literally what it says on the tin ✨


πŸ’– SYNOPSIS

void device_links_driver_cleanup (struct device *dev );

returns nothing, takes one device, does the tidying 🧹


🫢 ARGUMENTS

  • dev β€” the device whose driver has just gone away 😭 like, it's gone, moved out, took the lamp. this is who we're cleaning up after.

✨ DESCRIPTION

so what actually happens: we update the links to consumers for dev by flipping their status to "dormant" 😴 (yes, in quotes, that's the status name, it's giving hibernation era), and then we invoke __device_links_no_driver to update links to suppliers for it as appropriate. two jobs, one function, main character energy fr fr πŸ‘‘

heads up bestie 🚨: links that don't have the DL_FLAG_MANAGED flag set are ignored. not managed = not our problem, we don't touch those. periodt.

πŸ‘‘ SEE ALSO

Kernel file ./drivers/base/core.c β€” that's where the source lives, go snoop πŸ¦‹ and here's the whole friend group, no cap, every single one:


πŸ’€ that's the whole list, i counted, don't come for me. okay love u bye πŸ“

mwah πŸ’‹ this page lives in ./drivers/base, it's the October 2026 edition of the Kernel API Manual, and it's called device_links_driver_cleanup(9) in case you forgot already πŸ™ˆ slay ✨

πŸ“¦ where this page comes from