__mei_me_cl_by_uuid_id(9)
π
__mei_me_cl_by_uuid_id(9) β Kernel API Manual vibes β¨
okay so this is the <pink>Kernel API Manual</pink> page for __mei_me_cl_by_uuid_id, and bestie, the name literally spills the tea right there: it locates a me client by client id and uuid β and yes, it increases the ref count π«Ά so don't ghost it afterward, mmmkay?
β¨ NAME β¨
__mei_me_cl_by_uuid_id β locate me client by client id and uuid, increases ref count π
π¦ SYNOPSIS π¦
struct mei_me_client * __mei_me_cl_by_uuid_id (struct mei_device *dev ,
const uuid_le *uuid , u8 client_id );
π ARGUMENTS π
devβ the device structure πΈuuidβ me client uuid β¨client_idβ me client id π«
π RETURN π
me client or null if not found β so like, check for NULL, no cap, or you'll be crying in the group chat π
π₯ DESCRIPTION π₯
Locking: dev->me_clients_rwsem π β the way that semaphore is holding it down the whole time, iconic.
π SEE ALSO π
Kernel file ./drivers/misc/mei/client.c and honestly, the whole friend group showed up:
mei_me_cl_init(9), mei_me_cl_get(9), mei_me_cl_release(9), mei_me_cl_put(9), __mei_me_cl_del(9), mei_me_cl_del(9), mei_me_cl_add(9), __mei_me_cl_by_uuid(9), mei_me_cl_by_uuid(9), mei_me_cl_by_id(9), mei_me_cl_by_uuid_id(9), mei_me_cl_rm_by_uuid(9), mei_me_cl_rm_all(9), mei_io_cb_free(9), mei_tx_cb_enqueue(9), mei_tx_cb_dequeue(9), mei_cl_set_read_by_fp(9), mei_io_cb_init(9), mei_io_list_flush_cl(9), mei_io_tx_list_free_cl(9), mei_io_rd_list_free_fp(9), mei_cl_free_pending(9), mei_cl_alloc_cb(9), mei_cl_enqueue_ctrl_wr_cb(9), mei_cl_read_cb(9), mei_cl_flush_queues(9), mei_cl_init(9), mei_cl_allocate(9), mei_cl_link(9), mei_cl_unlink(9), mei_hbuf_acquire(9), mei_cl_wake_all(9), mei_cl_set_disconnected(9), mei_cl_irq_disconnect(9), __mei_cl_disconnect(9), mei_cl_disconnect(9), mei_cl_is_other_connecting(9), mei_cl_send_connect(9), mei_cl_irq_connect(9), mei_cl_connect(9), mei_cl_alloc_linked(9), mei_cl_tx_flow_ctrl_creds(9), mei_cl_tx_flow_ctrl_creds_reduce(9), mei_cl_vtag_alloc(9), mei_cl_fp_by_vtag(9), mei_cl_reset_read_by_vtag(9), mei_cl_read_vtag_add_fc(9), mei_cl_vt_support_check(9), mei_cl_add_rd_completed(9), mei_cl_del_rd_completed(9), mei_cl_notify_fop2req(9), mei_cl_notify_req2fop(9), mei_cl_irq_notify(9), mei_cl_notify_request(9), mei_cl_notify(9), mei_cl_notify_get(9), mei_cl_read_start(9), mei_msg_hdr_init(9), mei_cl_irq_write(9), mei_cl_write(9), mei_cl_complete(9), mei_cl_all_disconnect(9), mei_cl_irq_dma_map(9), mei_cl_irq_dma_unmap(9), mei_cl_dma_alloc_and_map(9), mei_cl_dma_unmap(9)
like, that's the whole squad, periodt ππ
π§ tiny reminder from me to you: this one bumps the ref count, so pair it with a release/put situation and don't just leave it hanging π
okay that's the page!! π it ships out of ./drivers/misc/mei, dated October 2026, and it's the __mei_me_cl_by_uuid_id(9) entry in the Kernel API Manual β mwah, go be the main character of your driver code ππ¦π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms