device_for_e...reverse_from(9)

📦 version 7.3.1, in nixpkgs unstable

💅 device_for_e...reverse_from(9)

okay so this is a page from the Kernel API Manual and we're about to get into device_for_each_child_reverse_from — yes the name is a whole mouthful, yes it's iconic, let's go 🎀

✨ NAME ✨

device_for_each_child_reverse_from — the device child iterator, but make it reversed 💫 (it walks the child list backwards, bestie).

🌸 SYNOPSIS 🌸

int device_for_each_child_reverse_from (struct device *parent , struct
device *from , void *data , device_iter_t fn );

🦋 ARGUMENTS 🦋

  • parent — the parent struct device. like, the mom friend of the group chat 👑
  • from — optional starting point in the child list. optional!! so you can just pass NULL and vibe ✨
  • data — data for the callback. it gets handed straight to fn, no questions asked 🫶
  • fn — the function to be called for each device. your little callback bestie 💖

💜 DESCRIPTION 💜

So what this does: it iterates over parent's child devices, starting at from, and calls fn for each one, passing it data. lowkey simple, highkey useful 😌

Heads up! This helper is identical to device_for_each_child_reverse when from is NULL. no cap, literally the same behaviour in that case.

fn is checked each iteration. If it returns anything other than 0, the iteration stops and that value gets returned to the caller of device_for_each_child_reverse_from — so your callback's return value is the escape hatch, fr fr 💀 (also yes, the original sentence stops there mid-thought, we do not fix the kernel docs, we respect them 🙈).

🌈 SEE ALSO 🌈

Kernel file ./drivers/base/core.c, plus honestly a whole friend group of functions:

okay that's the whole thing, go iterate backwards and slay 💅✨

source ./drivers/base 🎀 dated October 2026 🌸 mwah, bye bestie 🫶💖

📦 where this page comes from