__for_each_daddr_next(9)

💅 __for_each_daddr_next(9) — Kernel API Manual, group-chat edition 💅

Okay so welcome to the __for_each_daddr_next(9) page, bestie. This is the Kernel API Manual entry, and we are absolutely not skipping a single detail. ✨

🌸 NAME 🌸

__for_each_daddr_next — iterates over the device addresses with pre-initialized iterator. That's the vibe: device addresses, iterator already pre-initialized, no cap. 💖

✨ SYNOPSIS ✨

__for_each_daddr_next (__dp , __iter , __step );

Literally that exact signature, spacing and all. Slay. 🫶

🎀 ARGUMENTS 🎀

• __dp — device address (output). The page labels it output, and that's the whole note. 💅
• __iter — the original page gives no description here. Not me leaving it blank—this is genuinely all the source says. It still gets its own bullet because we do not erase arguments in this house. 💀
• __step — step size. That's it, that's the whole description. 🌈

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/i915/i915_scatterlist.h
• __sg_next(9)
• __for_each_sgt_daddr(9)
• for_each_sgt_page(9)
• i915_sg_dma_sizes(9)
• struct i915_refct_sgt_ops(9)
• struct i915_refct_sgt(9)
• i915_refct_sgt_put(9)
• i915_refct_sgt_get(9)
• __i915_refct_sgt_init(9)

bestie, the original page really does leave __iter with zero description, and we are respecting the source. no invented lore, periodt. 💖

xoxo, this came from ./drivers/gpu/drm/i915, dated October 2026, and the page is __for_each_daddr_next(9) — mwah 💋