cec_msg_recv_is_rx_result(9)

💅 cec_msg_recv_is_rx_result — bestie, is this the reply you've been waiting for??

okay so this one lives in the Kernel API Manual (yes, the Kernel API Manual, we're in the big leagues now 🎀), and honestly the name says it all: cec_msg_recv_is_rx_result returns true if this message contains the reply of an earlier non-blocking transmit. that's it. that's the whole vibe check. ✨

✨ SYNOPSIS ✨

int cec_msg_recv_is_rx_result (const struct cec_msg *msg );

she's a little function, she takes one pointer, she returns an int. short and iconic, no notes. 👑

🫶 ARGUMENTS 🫶

• msg — the message structure from CEC_RECEIVE. that's the one you gotta hand over, bestie. literally the thing you pulled out with CEC_RECEIVE, and this function will tell you if it's the reply you were lowkey waiting on. 🦋

ngl, the whole point is: you did a non-blocking transmit earlier, you didn't sit there blocking like a fool, and now something came in — is this the answer to that? true = yes ma'am. 💖

🌈 SEE ALSO 🌈

the full friend group, no one left out, fr fr:

• Kernel file ./include/uapi/linux/cec.h and struct cec_msg(9)
• cec_msg_initiator(9)
• cec_msg_destination(9)
• cec_msg_opcode(9)
• cec_msg_is_broadcast(9)
• cec_msg_init(9)
• cec_msg_set_reply_to(9)
• cec_msg_recv_is_tx_result(9) — her sister, the tx-side twin, go say hi 💅
• struct cec_caps(9)
• struct cec_log_addrs(9)
• struct cec_drm_connector_info(9)
• struct cec_connector_info(9)
• struct cec_event_state_change(9)
• struct cec_event_lost_msgs(9)
• struct cec_event(9)

and that's the whole page, babes 🍓 this little icon ships out of ./include/uapi/linux and it's stamped October 2026 — so yeah, mark your calendar, the future is now, and cec_msg_recv_is_rx_result(9) ate. periodt. 🧚‍♀️💜🔥