device_link_remove(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, welcome to device_link_remove(9) from the Kernel API Manual 🫢. This is the page for the function whose NAME card literally says: device_link_remove β€” Delete a stateless link between two devices. slay πŸ’…


🌸 SYNOPSIS 🌸

The signature is exactly this, no edits, no vibes-based renaming:

void device_link_remove (void *consumer , struct device *supplier );

It’s void, so there’s no return value to catch β€” it’s giving β€œjust make the call” energy ✨.

πŸŽ€ ARGUMENTS πŸŽ€

  • consumer β€” Consumer end of the link. πŸ’–
  • supplier β€” Supplier end of the link. πŸ¦‹

πŸ’… DESCRIPTION πŸ’…

The caller must ensure proper synchronization of this function with runtime PM. That’s the whole vibe check, and it is not optional 😭.

⚠️ Bestie, do not skip the sync: the caller must ensure proper synchronization of this function with runtime PM. The function is void, but the synchronization responsibility is very much main-character energy πŸ’€.

πŸ‘€ SEE ALSO πŸ‘€

Kernel file: ./drivers/base/core.c β€” and the whole friend group is:


Signing off from source/version ./drivers/base, dated October 2026, page device_link_remove(9) β€” bye bestie, go sync that runtime PM πŸ«ΆπŸ’–

πŸ“¦ where this page comes from