DECLARE_NEXT_HOLE_ADDR(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DECLARE_NEXT_HOLE_ADDR(9) πŸ’…

ok so bestie, welcome to the Kernel API Manual β€” this one's a macro page, subsection 9, and no cap it's giving "tiny macro, very demure, extremely important" energy. let's get into it πŸŽ€


✨ NAME ✨

DECLARE_NEXT_HOLE_ADDR β€” it's literally a macro that declares next hole functions. that's the whole vibe. πŸ•³οΈβœ¨


🌸 SYNOPSIS 🌸

DECLARE_NEXT_HOLE_ADDR (name , first , last );

look at her. three args, no notes. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • name β€” the name of the function you're declaring. yes babe you get to pick it, main character energy fr.
  • first β€” the first rb member to traverse. and it has to be either rb_left or rb_right β€” pick one, king πŸ‘‘
  • last β€” the last rb member to traverse. also either rb_right or rb_left. yes it's the mirror of first, we love symmetry πŸ’«

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea β˜• β€” this macro declares a function that returns the next hole of the addr rb tree. like, the function that goes hunting for the next gap. πŸ•³οΈπŸ”

and while we're traversing the tree, we take the searched size into account. the way that this is so smart?? 😭 we only visit branches that have potential big enough holes. no wasting time on tiny gaps, we're not doing that today. efficiency slay. πŸ’…πŸ”₯


🌈 SEE ALSO 🌈

the whole squad, assembled ⭐:

go read them, iykyk πŸ§šπŸ’–


ngl bestie, this page lives in ./drivers/gpu/drm and it's stamped October 2026 β€” so if you're reading DECLARE_NEXT_HOLE_ADDR(9) and it's not October 2026 anymore, that's just the version tag doing its thing. mwah, bye πŸ’‹πŸŽ€βœ¨
πŸ“¦ where this page comes from