mei_cl_bus_module_get(9)

💖 mei_cl_bus_module_get(9) 💖

okay so welcome to the mei_cl_bus_module_get(9) page from the Kernel API Manual, bestie. This one is short, but it's giving “important little helper” energy fr fr.

🎀 NAME 🎀

mei_cl_bus_module_get — acquire module of the underlying hw driver. That's the whole assignment, no cap.

✨ SYNOPSIS ✨

bool mei_cl_bus_module_get (struct mei_cl_device *cldev );

🫶 ARGUMENTS 🫶

• cldev — mei client device. That's the one you're handing over, bestie.

🌈 RETURN 🌈

• true on success — slay.
• false if the module was removed — oop, that's the vibe check failing.

💅 SEE ALSO 💅

The kernel file is ./drivers/misc/mei/bus.c, and these pages are all in the group chat:

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

Source/version: ./drivers/misc/mei · date: October 2026 · page: mei_cl_bus_module_get(9). Bye bestie, go get that module 💜✨