mei_cl_bus_vtag(9)

✨ NAME ✨

okay bestie, this is mei_cl_bus_vtag(9) from the Kernel API Manual, and it's literally the “get bus vtag entry wrapper” girlie. The tag for bus client is always first — that's the whole vibe, no cap. 💅

---

🦋 SYNOPSIS 🦋

the signature is exactly this:

struct mei_cl_vtag * mei_cl_bus_vtag (struct mei_cl *cl );

---

🌸 ARGUMENTS 🌸

one argument, bestie:

• cl — host client. that's it. that's the whole argument. 🎀

---

⭐ RETURN ⭐

it hands you back the bus vtag or NULL. simple as that. 💖

---

🫶 SEE ALSO 🫶

the whole friend group is tagged in below, starting with 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_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_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)

---

mwah 💋 — source/version: ./drivers/misc/mei; date: October 2026. this has been mei_cl_bus_vtag(9), and yes, the tag for bus client is always first. bye bestie 🫶✨