mei_cldev_set_drvdata(9)
π mei_cldev_set_drvdata(9) β Kernel API Manual π
β¨ NAME β¨
mei_cldev_set_drvdata β the driver data setter, periodt π
πΈ SYNOPSIS πΈ
bestie, the whole signature is right here, so copy it exactly:
void mei_cldev_set_drvdata (struct mei_cl_device *cldev , void *data );
π¦ ARGUMENTS π¦
cldevβ the mei client device, aka the device main character π«Άdataβ the data to store, literally the payload vibe πΎ
π SEE ALSO π
okay so the Kernel file is ./drivers/misc/mei/bus.c, and the whole bestie lineup is: __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_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 bestie, source/version check before you go: this one comes from ./drivers/misc/mei, dated October 2026, and itβs literally the mei_cldev_set_drvdata(9) page. byeee, ily, slay π
β¨
π¦ 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