api_cmd_set_status_addr(9)

💖 NAME 💖

api_cmd_set_status_addr — okay so this one sets the status address of a chain in the HW. That's it, that's the whole vibe. One job, does it slayfully ✨

(this is page 9 of the Kernel API Manual, bestie — kernel-space only, no userland shenanigans 🫶)

✨ SYNOPSIS ✨

void api_cmd_set_status_addr (struct hinic_api_cmd_chain *chain );

Bestie it returns void. Nothing comes back. It's giving "I did the thing, don't ask me for a receipt" 💅

🎀 ARGUMENTS 🎀

• chain — the API CMD specific chain that we're setting the HW status address for. Like, this chain. The one you're handing over. That's the one getting its status address set in the hardware, no cap 🌸

🦋 SEE ALSO 🦋

So the actual source lives in the kernel file ./drivers/net/ethernet/huawei/hinic/hinic_hw_api_cmd.c — go read it, it ate 👑

And here's the whole friend group, every single one of them, not a single mutual left out:

• chain_busy(9)
• get_cell_data_size(9)
• prepare_cell_ctrl(9)
• prepare_api_cmd(9)
• prepare_cell(9)
• api_cmd_status_update(9)
• wait_for_status_poll(9)
• wait_for_api_cmd_completion(9)
• api_cmd(9)
• hinic_api_cmd_write(9)
• api_cmd_hw_restart(9)
• api_cmd_ctrl_init(9)
• api_cmd_set_num_cells(9)
• api_cmd_head_init(9)
• api_cmd_chain_hw_clean(9)
• api_cmd_chain_hw_init(9)
• free_cmd_buf(9)
• alloc_cmd_buf(9)
• api_cmd_create_cell(9)
• api_cmd_destroy_cell(9)
• api_cmd_destroy_cells(9)
• api_cmd_create_cells(9)
• api_chain_init(9)
• api_chain_free(9)
• api_cmd_create_chain(9)
• api_cmd_destroy_chain(9)
• hinic_api_cmd_init(9)
• hinic_api_cmd_free(9)

Okay that's the whole page, mwah 💋 This little icon comes to you from source ./drivers/net/ethernet/huawei/... and it's dated October 2026 — so mark your calendars and stan responsibly, bestie 🎀🦋✨