mei_cl_bus_notify_event(9)

🌸 NAME 🌸

okay so bestie, welcome to mei_cl_bus_notify_event(9) — yes, that's the Kernel API Manual page, and the whole name-section vibe is literally: mei_cl_bus_notify_event — schedule notify cb on bus client. 💅

✨ SYNOPSIS ✨

the signature is giving one-liner main character energy:

bool mei_cl_bus_notify_event (struct mei_cl *cl );

🎀 ARGUMENTS 🎀

• cl — host client. that's it, that's the arg. 🫶

🔥 RETURN 🔥

• true if event was scheduled
• false if the client is not waiting for event

no cap, that's the whole return situation. 😭

💖 SEE ALSO 💖

Kernel file ./drivers/misc/mei/bus.c is the home base, and here is the entire ref squad — every single one, zero skipped, periodt:

• __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_rx_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)

signed off from source/version ./drivers/misc/mei, dated October 2026 — mei_cl_bus_notify_event(9) out! 🫶💖