mei_cl_is_single_recv_buf(9)

💅 mei_cl_is_single_recv_buf(9) 💅

okay bestie, welcome to the Kernel API Manual ✨ — this one's a lil function from the kernel side of things and honestly? she's short, she's sweet, she's giving "one job and she does it." 🌸

---

🎀 NAME 🎀

mei_cl_is_single_recv_buf — the vibe check that tells you whether the me client is using a single receiving buffer 🦋

---

✨ SYNOPSIS ✨

bool mei_cl_is_single_recv_buf (const struct mei_cl *cl );

like, that's it. that's the whole signature. no cap. 💅

---

🌈 ARGUMENTS 🌈

• cl — the host client 💖 (that's the thing you're asking about, bestie, don't forget to actually pass it)

---

👑 RETURN 👑

Returns true if single_recv_buf == 1; 0 otherwise 🫶

fr fr that's the whole contract — either it's a single recv buffer or it's not, there is no in-between ✨

---

💜 SEE ALSO 💜

Kernel file ./drivers/misc/mei/client.h — go read it, iykyk 📖

and the whole friend group of related calls, all iconic in their own right:

• mei_me_cl_is_active(9)
• mei_me_cl_uuid(9)
• mei_me_cl_ver(9)
• mei_me_cl_max_conn(9)
• mei_me_cl_fixed(9)
• mei_me_cl_vt(9)
• mei_me_cl_max_len(9)
• mei_cl_is_connected(9)
• mei_cl_me_id(9)
• mei_cl_mtu(9)
• mei_cl_is_fixed_address(9)
• mei_cl_uuid(9)
• mei_cl_host_addr(9)

---

okay that's the whole page, mwah 💋 — this cutie lives in ./drivers/misc/mei, she's dated October 2026, and she answers to mei_cl_is_single_recv_buf(9) 🧚‍♀️ go forth and check those buffers, bestie 💖🔥