mei_me_cl_by_uuid_id(9)

📦 version 7.3.1, in nixpkgs unstable

💅 mei_me_cl_by_uuid_id(9) — from the Kernel API Manual, bestie

okay so picture this: you're deep in the mei subsystem and you need to find one specific me client, and you've got both its uuid and its client id to go on. that's the whole vibe of this function. it locates the me client by client id and uuid, and — no cap — it bumps the ref count while it's at it. 🎀

✨ SYNOPSIS ✨

struct mei_me_client * mei_me_cl_by_uuid_id (struct mei_device *dev ,
const uuid_le *uuid , u8 client_id );

she's a three-argument girlie and she returns a pointer, periodt. 🫶

🌸 ARGUMENTS 🌸

  • dev — the device structure. the whole device. your main character. 👑
  • uuid — the me client uuid. type is const uuid_le *, so she's a pointer, and she's const. respect. ✨
  • client_id — the me client id. it's a u8, so it's smol. 🍓

💖 RETURN 💖

you get the me client, or null if it's not found. that's it, that's the answer. if it's null, it's giving "she's not here" energy. 😭

and remember — the NAME section says this one increases ref count. so when you're done, she needs her ref count handled properly, bestie, don't just leave her hanging. 💅

🔥 SEE ALSO 🔥

this list is long and honestly iconic. it's all from the kernel file ./drivers/misc/mei/client.c, and the whole found family is here:

iykyk — that's the whole squad. 💜

and that's the page, bestie!! this little gem lives in ./drivers/misc/mei, and the footer says October 2026 with the manual source/version line mei_me_cl_by_uuid_id(9) — so yeah, it's got a date, it's got a name, she's fully official. go forth and find your client. 🦋💖

📦 where this page comes from