device_move(9)

📦 version 7.3.1, in nixpkgs unstable

💅 device_move(9) — the Kernel API Manual page, bestie edition

okay so real talk, this is a page from the Kernel API Manual — yes, the Kernel one, not the syscall one — and it's about the single most "moving day" function in the whole device model. buckle up 🎀

✨ NAME ✨

device_move — moves a device to a new parent 🦋

like, literally picks the device up, boxes up its little kobjects, and rehomes it. iconic behavior honestly.

✨ SYNOPSIS ✨

int device_move (struct device *dev , struct device *new_parent , enum
dpm_order dpm_order );

spaces before the commas are load-bearing, do not touch them 💀

✨ ARGUMENTS ✨

  • dev — the pointer to the struct device that's getting moved. this is your main character, the one packing its bags 💖
  • new_parent — the new parent of the device. and yes, it can be NULL — no cap, that's allowed 🌸
  • dpm_order — how to reorder the dpm_list. that's the whole description, bestie, it's giving "figure out your ordering situation" ✨

✨ SEE ALSO ✨

okay this is the part where the page just goes feral and name-drops the entire friend group. source file first:

Kernel file ./drivers/base/core.c

and now, the full squad, in exact order, no one gets left out 🫶:

okay and that's the whole page!! it lives over in ./drivers/base, dated October 2026, and it signs off with device_move(9) like the little legend it is 💜 thanks for reading bestie, go rehome some devices responsibly 🧚✨

📦 where this page comes from