hinic_cmdq_direct_resp(9)
π 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 π§
hinic_alloc_cmdq_buf(9)hinic_free_cmdq_buf(9)hinic_set_arm_bit(9)cmdq_arm_ceq_handler(9)cmdq_sync_cmd_handler(9)cmdq_ceq_handler(9)cmdq_init_queue_ctxt(9)init_cmdq(9)free_cmdq(9)init_cmdqs_ctxt(9)hinic_init_cmdqs(9)hinic_free_cmdqs(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms