hinic_ceq_register_cb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hinic_ceq_register_cb(9) β€” NAME πŸ’…

okay so bestie, welcome to the Kernel API Manual section 9 page for hinic_ceq_register_cb β€” and yes, this is literally the function that registers a CEQ callback for a specific event. that's it, that's the whole vibe. ✨


πŸŽ€ SYNOPSIS πŸŽ€

void hinic_ceq_register_cb (struct hinic_ceqs *ceqs , enum
hinic_ceq_type event , void *handle , void (*handler)(void *handle, u32
ceqe_data) );

no cap, that's the exact signature β€” return type void, four arguments, and the callback takes a u32 ceqe_data as its second param. copy it character for character, i promise it matters. 🫢


🌸 ARGUMENTS 🌸

  • ceqs β€” pointer to the Completion eqs part of the chip. like, the whole CEQ party is behind this pointer and you're handing over the guest list. πŸ’–
  • event β€” the ceq event you're registering a callback for. one event, one callback, that's the deal. πŸ¦‹
  • handle β€” private data that will be used by the callback. your little secret stash, passed straight through. πŸ™ˆ
  • handler β€” the callback function itself. the main character. it gets void *handle and u32 ceqe_data and does its thing. πŸ‘‘
lowkey the whole point: you're wiring up this event on this ceqs to this handler, carrying this handle along for the ride. periodt. πŸ’…

🌈 SEE ALSO 🌈

first up, the source itself, iykyk:

  • Kernel file ./drivers/net/ethernet/huawei/hinic/hinic_hw_eqs.c

and the whole friend group β€” go say hi, they're all iconic:


and that's the page, bestie 🧚✨ quick little sign-off: this beauty comes from ./drivers/net/ethernet/huawei/... and it's dated October 2026 β€” so yes, it's giving future icon. πŸ“πŸ’œ bye!! πŸŽ€

πŸ“¦ where this page comes from