fm10k_mbx_disconnect(9)

💅 fm10k_mbx_disconnect(9) 💅

okay so bestie, welcome to the Kernel API Manual entry for fm10k_mbx_disconnect(9) — it's giving "saying goodbye to your mailbox but make it a whole procedure" energy and honestly? iconic. ✨

---

🌸 NAME 🌸

fm10k_mbx_disconnect — shutdown mailbox connection 🫶

---

✨ SYNOPSIS ✨

void fm10k_mbx_disconnect (struct fm10k_hw *hw , struct fm10k_mbx_info
*mbx );

like literally that's the whole signature, no notes 💅

---

🎀 ARGUMENTS 🎀

• hw — pointer to hardware structure 🦋
• mbx — pointer to mailbox 💌

---

💖 DESCRIPTION 💖

So this function will shut down the mailbox. periodt. 💀

The way it works is: it places the mailbox first in the disconnect state, then it allows up to a predefined timeout for the mailbox to transition to close on its own — like giving it a lil grace period to sort itself out, main character energy 🧚

If this does not occur, then the mailbox will be forced into the closed state. no negotiation, no vibe check, it's just done 🙈

⚠️ ok important thing bestie: any mailbox transactions not completed before calling this function are not guaranteed to complete and may be dropped. so like, finish your stuff first, iykyk 😭

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/net/ethernet/intel/fm10k/fm10k_mbx.c — go read it, it's literally right there 💜

And the whole friend group, in order:

fm10k_fifo_init(9), fm10k_fifo_used(9), fm10k_fifo_unused(9), fm10k_fifo_empty(9), fm10k_fifo_head_offset(9), fm10k_fifo_tail_offset(9), fm10k_fifo_head_len(9), fm10k_fifo_head_drop(9), fm10k_fifo_drop_all(9), fm10k_mbx_index_len(9), fm10k_mbx_tail_add(9), fm10k_mbx_tail_sub(9), fm10k_mbx_head_add(9), fm10k_mbx_head_sub(9), fm10k_mbx_pushed_tail_len(9), fm10k_fifo_write_copy(9), fm10k_fifo_enqueue(9), fm10k_mbx_validate_msg_size(9), fm10k_mbx_write_copy(9), fm10k_mbx_pull_head(9), fm10k_mbx_read_copy(9), fm10k_mbx_push_tail(9), fm10k_crc_16b(9), fm10k_fifo_crc(9), fm10k_mbx_update_local_crc(9), fm10k_mbx_verify_remote_crc(9), fm10k_mbx_rx_ready(9), fm10k_mbx_tx_ready(9), fm10k_mbx_tx_complete(9), fm10k_mbx_dequeue_rx(9), fm10k_mbx_enqueue_tx(9), fm10k_mbx_read(9), fm10k_mbx_write(9), fm10k_mbx_create_connect_hdr(9), fm10k_mbx_create_data_hdr(9), fm10k_mbx_create_disconnect_hdr(9), fm10k_mbx_create_fake_disconnect_hdr(9), fm10k_mbx_create_error_msg(9), fm10k_mbx_validate_msg_hdr(9), fm10k_mbx_create_reply(9), fm10k_mbx_reset_work(9), fm10k_mbx_update_max_size(9), fm10k_mbx_connect_reset(9), fm10k_mbx_process_connect(9), fm10k_mbx_process_data(9), fm10k_mbx_process_disconnect(9), fm10k_mbx_process_error(9), fm10k_mbx_process(9), fm10k_mbx_connect(9), fm10k_mbx_validate_handlers(9), fm10k_mbx_register_handlers(9), fm10k_pfvf_mbx_init(9), fm10k_sm_mbx_create_data_hdr(9), fm10k_sm_mbx_create_connect_hdr(9), fm10k_sm_mbx_connect_reset(9), fm10k_sm_mbx_connect(9), fm10k_sm_mbx_disconnect(9), fm10k_sm_mbx_validate_fifo_hdr(9), fm10k_sm_mbx_process_error(9), fm10k_sm_mbx_create_error_msg(9), fm10k_sm_mbx_receive(9), fm10k_sm_mbx_transmit(9), fm10k_sm_mbx_create_reply(9), fm10k_sm_mbx_process_reset(9), fm10k_sm_mbx_process_version_1(9), fm10k_sm_mbx_process(9), fm10k_sm_mbx_init(9)

like that's the entire group chat, all present and accounted for 👑

---

⭐ one last lil sign-off ⭐

This lil page came from ./drivers/net/ethernet/intel/f... and it's dated October 2026 — slay, see you in the next one bestie 💅💖🌸