hinic_aeq_unregister_hw_cb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– hinic_aeq_unregister_hw_cb(9) β€” a Kernel API Manual moment πŸ’–

okay so bestie, we're deep in the Kernel API Manual today and honestly? this one's a little icon. it's a void-returning function, it's from the huawei hinic driver family, and its whole personality is un-doing a thing. no notes. πŸ’…


✨ NAME ✨

hinic_aeq_unregister_hw_cb β€” literally just unregistering the AEQ callback for one specific event πŸŽ€

like, you had a callback registered for a particular event? this is the girl that takes it back off the list. no cap, that's the whole gig.


πŸ¦‹ SYNOPSIS πŸ¦‹

void hinic_aeq_unregister_hw_cb (struct hinic_aeqs *aeqs , enum
hinic_aeq_type event );

she takes two things, she returns nothing (void, my beloved), and she's out. main character energy but make it minimal. ⭐


🌸 ARGUMENTS 🌸

  • aeqs β€” pointer to the Async eqs of the chip πŸ’œ this is the whole eq situation for the chip, and you're handing her the address of it.
  • event β€” the aeq event to unregister the callback for it πŸ”₯ so you point at which event you want the callback removed from. specific. targeted. obsessed.
heads up bestie: it's void, so there's literally no return value to check β€” no exit status, no error code, nothing to catch. just vibes and a return. 🫢

🌈 SEE ALSO 🌈

the source of truth lives right here in the kernel tree, iykyk:

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

and the whole friend group she runs with β€” same file, same energy:


and that's the page, bestie!! 🧚 go unregister something responsibly ✨

πŸŽ€ sign-off szn: this cutie came from ./drivers/net/ethernet/huawei/... and it's dated October 2026, so yeah β€” future girl manual, we love to see it. πŸ’–πŸ™ˆ
πŸ“¦ where this page comes from