device_pm_move_after(9)

📦 version 7.3.1, in nixpkgs unstable

✨ device_pm_move_after 💅

okay so bestie, welcome to the Kernel API Manual page for device_pm_move_after(9) — yes that's the section 9 vibe, kernel-internals territory, we're so back 🫶

🌸 NAME 🌸

device_pm_move_after — literally just moves a device around in the PM core's list of active devices. that's it. that's the whole job. slay 🎀

⭐ SYNOPSIS ⭐

void device_pm_move_after (struct device *deva , struct device *devb );

no cap, that's the whole signature. two devices in, zero return value out, iconic behaviour 💅

🦋 ARGUMENTS 🦋

  • deva — the device you're moving, in dpm_list. she's the main character of this operation ✨
  • devb — the device that deva should come after. so deva goes right behind devb in the list, iykyk 🎯

🔥 SEE ALSO 🔥

Kernel file ./drivers/base/power/main.c — that's where the magic lives, go read it, ngl 🌈

💀 reminder: list order in the PM core is not a lil cosmetic thing, so don't go shuffling devices around for fun. this is a real API with real consequences, periodt.

and that's the page, bestie 🌸 this lil doc came from ./drivers/base/power, dropped in October 2026, and it's the device_pm_move_after(9) page from the Kernel API Manual. go forth and reorder responsibly 🧚💜

📦 where this page comes from