hinic_cmdq_direct_resp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hinic_cmdq_direct_resp ✨

okay so welcome to the Kernel API Manual bestie, this page is all about hinic_cmdq_direct_resp and honestly it's giving "one job, does it well" energy πŸŽ€


🌸 NAME 🌸

hinic_cmdq_direct_resp β€” send a command with direct data as the response, no cap 🫢


⭐ SYNOPSIS ⭐

int hinic_cmdq_direct_resp (struct hinic_cmdqs *cmdqs , enum
hinic_mod_type mod , u8 cmd , struct hinic_cmdq_buf *buf_in , u64 *resp
);

like look at her, five arguments, very demure, very mindful πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cmdqs β€” the cmdqs. that's the whole assignment, she's just the cmdqs ✨
  • mod β€” the module on the card that will handle the command, iykyk which one you're talking to πŸ‘‘
  • cmd β€” the command, the actual thing you want to happen πŸ”₯
  • buf_in β€” the buffer for the command, this is where your stuff lives πŸŽ€
  • resp β€” the response to return, so the answer comes back through here 🌈

πŸ’– DESCRIPTION πŸ’–

Return 0 β€” Success. Negative β€” Failure. that's it, that's the whole vibe check 😭 slay when it's zero, πŸ’€ when it's negative, periodt.


🌟 SEE ALSO 🌟

Kernel file ./drivers/net/ethernet/huawei/hinic/hinic_hw_cmdq.c β€” go read the source bestie, it's right there 🧚

the whole friend group honestly, obsessed with all of them πŸ«ΆπŸ’œ


ngl this page is short but she ate. no invented behaviour, no extra lore, just the facts with a little glitter on top ✨

and that's a wrap bestie πŸŽ€ this gem came out of ./drivers/net/ethernet/huawei/... dated October 2026, footer said hinic_cmdq_direct_resp(9) and honestly she said it with her whole chest πŸ’…πŸ’– bye bye now, go call the function πŸ¦‹

πŸ“¦ where this page comes from