mucse_read_mbx_pf(9)

💖 NAME 💖

okay so this is the Kernel API Manual page for mucse_read_mbx_pf(9) — and the name is literally:

mucse_read_mbx_pf - Read a message from the mailbox 💌

✨ SYNOPSIS ✨

bestie, here's the signature — keep it exactly like this, no edits, no cap:

int mucse_read_mbx_pf (struct mucse_hw *hw , __le32 *msg , u16 size );

🫶 ARGUMENTS 🫶

• hw — pointer to the HW structure
• msg — the message buffer
• size — length of buffer

🧚 DESCRIPTION 🧚

Okay so real talk: mucse_read_mbx_pf copies a message from the mbx buffer to the caller's memory buffer. The presumption is that the caller knows that there was a message due to a fw request, so no polling for message is needed. It's giving "already knows the tea, just reading the text" 💅.

🌈 RETURN 🌈

• 0 on success ✅
• negative errno on failure 😭

🔗 SEE ALSO 🔗

The Kernel file is ./drivers/net/ethernet/mucse/rnpgbe/rnpgbe_mbx.c — and here's the whole ref squad, no skips:

• mbx_data_rd32(9)
• mbx_data_wr32(9)
• mbx_ctrl_rd32(9)
• mbx_ctrl_wr32(9)
• mucse_mbx_get_lock_pf(9)
• mucse_obtain_mbx_lock_pf(9)
• mucse_release_mbx_lock_pf(9)
• mucse_mbx_get_fwreq(9)
• mucse_mbx_inc_pf_ack(9)
• mucse_check_for_msg_pf(9)
• mucse_poll_for_msg(9)
• mucse_poll_and_read_mbx(9)
• mucse_mbx_get_fwack(9)
• mucse_mbx_inc_pf_req(9)
• mucse_write_mbx_pf(9)
• mucse_check_for_ack_pf(9)
• mucse_poll_for_ack(9)
• mucse_write_and_wait_ack_mbx(9)
• mucse_mbx_reset(9)
• mucse_init_mbx_params_pf(9)

xoxo, your kernel bestie 💅 — source/version: ./drivers/net/ethernet/mucse/r..., date: October 2026, page mucse_read_mbx_pf(9).