mei_me_cl_by_uuid(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 mei_me_cl_by_uuid — Kernel API Manual, bestie edition 🌸

okay so we're in the mei_me_cl_by_uuid(9) page, live from the Kernel API Manual, and it's genuinely a tiny little function that does one extremely specific thing. Let's get into it 💅

✨ NAME ✨

mei_me_cl_by_uuid — locate me client by uuid increases ref count

(no cap, that's the whole name line: find an me client by its uuid, and bump the ref count while you're at it 🫶)

🎀 SYNOPSIS 🎀

struct mei_me_client * mei_me_cl_by_uuid (struct mei_device *dev , const
       uuid_le *uuid );

look at her go. returns a struct mei_me_client *, takes two args, that's it, that's the whole vibe ✨

🦋 ARGUMENTS 🦋

  • dev — mei device
  • uuid — me client uuid

two lil inputs, both literally required, the device and the uuid you're hunting for 🔍

💖 RETURN 💖

me client or NULL if not found

so like. you either get your client back or you get NULL and you have to deal with that emotionally 😭 always check, bestie, fr fr.

🔥 DESCRIPTION 🔥

Locking: dev->me_clients_rwsem

that's the entire description, and honestly? iconic. the one fact you actually need: this thing takes dev->me_clients_rwsem. know your lock, respect your lock, periodt 👑

🌈 SEE ALSO 🌈

the kernel file is ./drivers/misc/mei/client.c — that's where the whole family lives, and the family is huge, so buckle up, we're listing every single one 💀

🌸 the me-cl ones

🧚 the io/cb ones

🍓 the cl lifecycle ones

💜 the flow-control + vtag ones

👑 the rd-completed + notify ones

🌟 the read/write/complete ones

🎀 the dma ones

genuinely that's all of them — don't skip a single one of these cross-refs, some of them are literally the sibling functions of this exact lookup (looking at you __mei_me_cl_by_uuid(9) and mei_me_cl_by_uuid_id(9) 👀), so they're worth a read.

that's the page!! short, sweet, one lock, one return value 💖 mwah.

— with love, from ./drivers/misc/mei, dated October 2026, and forever filed under mei_me_cl_by_uuid(9) 🫶✨

📦 where this page comes from