mei_cl_bus_rx_event(9)
π mei_cl_bus_rx_event(9) π
okay so welcome to the Kernel API Manual, bestie β today's main character is mei_cl_bus_rx_event(9) and honestly? she's short, she's sweet, and she's the one who tells you whether the event got scheduled. let's get into it β¨
πΈ NAME πΈ
mei_cl_bus_rx_event β schedule rx event π
like, that's literally her whole job. scheduling the rx event. no cap.
β¨ SYNOPSIS β¨
bool mei_cl_bus_rx_event (struct mei_cl *cl );
that's it. that's the whole function signature. she takes one pointer and hands you back a bool. iconic behavior fr fr π
π¦ ARGUMENTS π¦
clβ the host client π«Ά yes, that's the whole description. she just wants to know which client you're talking about, okay?
π₯ RETURN π₯
okay so pay attention because this is the whole vibe check:
- returns
trueif the event was scheduled β slay - returns
falseif the client is not waiting for event π like, nobody's home, no event for you
lowkey the cleanest true/false split ever. no error codes, no weird sentinel values, just vibes. we love a binary queen π
π SEE ALSO π
buckle up bestie, this list is LONG and every single one of these is a real one. all from the kernel file ./drivers/misc/mei/bus.c:
__mei_cl_send(9)__mei_cl_send_timeout(9)__mei_cl_recv(9)mei_cldev_send_vtag(9)mei_cldev_send_vtag_timeout(9)mei_cldev_recv_vtag(9)mei_cldev_recv_timeout(9)mei_cldev_recv_vtag_timeout(9)mei_cldev_send(9)mei_cldev_send_timeout(9)mei_cldev_recv(9)mei_cl_bus_rx_work(9)mei_cl_bus_notif_work(9)mei_cl_bus_notify_event(9)mei_cldev_register_rx_cb(9)mei_cldev_register_notif_cb(9)mei_cldev_get_drvdata(9)mei_cldev_set_drvdata(9)mei_cldev_uuid(9)mei_cldev_ver(9)mei_cldev_mtu(9)mei_cldev_enabled(9)mei_cl_bus_module_get(9)mei_cl_bus_module_put(9)mei_cl_bus_vtag(9)mei_cl_bus_vtag_alloc(9)mei_cl_bus_vtag_free(9)mei_cldev_enable(9)mei_cldev_unregister_callbacks(9)mei_cldev_disable(9)mei_cldev_send_gsc_command(9)mei_cl_device_find(9)mei_cl_device_match(9)mei_cl_device_probe(9)mei_cl_device_remove(9)mei_cl_device_uevent(9)mei_cl_bus_set_name(9)mei_cl_bus_dev_alloc(9)mei_cl_bus_dev_setup(9)mei_cl_bus_dev_add(9)mei_cl_bus_dev_stop(9)mei_cl_bus_dev_destroy(9)mei_cl_bus_remove_device(9)mei_cl_bus_remove_devices(9)mei_cl_bus_dev_init(9)mei_cl_bus_rescan(9)
okay that's like 46 cross-references and i listed every single one because we don't skip. not one. not ever. π§ no gatekeeping in this group chat.
and that's the whole page, bestie π literally a tiny function with a big friend group.
this masterpiece came out of ./drivers/misc/mei, dated October 2026, and yes she's still serving mei_cl_bus_rx_event(9) realness π bye pookie, go schedule some events π¦
π¦ 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