mei_io_list_flush_cl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mei_io_list_flush_cl (9) β€” kernel API manual, bestie edition πŸŽ€

okay so this one lives in the Kernel API Manual, and it's lowkey a little cleanup crew. one function, does exactly one thing, no notes. let's get into it ✨


✨ NAME ✨

mei_io_list_flush_cl β€” removes cbs belonging to the cl. that's it. that's the whole job. she comes in, she clears out the callbacks that belong to a specific client, she leaves. main character energy fr fr πŸ’…


🌸 SYNOPSIS 🌸

void mei_io_list_flush_cl (struct list_head *head , const struct mei_cl
*cl );

so she takes a list head and a client, and she returns void β€” no return value, no "did it work", she just does it and ghosts. iconic πŸ¦‹


πŸ’– ARGUMENTS πŸ’–

  • head β€” an instance of our list structure. like, our list, the one we're flushing from. this is the list she's gonna walk through and sweep. 🧹
  • cl β€” host client. the client whose cbs are getting the boot. if a cb belongs to this cl, it's outta there. sorry not sorry πŸ™ˆ
both args are required, bestie β€” there's no version of this call that works with only one of them.

πŸ¦‹ SEE ALSO πŸ¦‹

the kernel file for all this is ./drivers/misc/mei/client.c β€” that's where the source lives, go read it if you're feeling brave πŸ’œ

and here's the whole friend group, all of them (9) pages, all of them in the neighborhood:

mei_me_cl_init(9), mei_me_cl_get(9), mei_me_cl_release(9), mei_me_cl_put(9), __mei_me_cl_del(9), mei_me_cl_del(9), mei_me_cl_add(9), __mei_me_cl_by_uuid(9), mei_me_cl_by_uuid(9), mei_me_cl_by_id(9), __mei_me_cl_by_uuid_id(9), mei_me_cl_by_uuid_id(9), mei_me_cl_rm_by_uuid(9), mei_me_cl_rm_all(9), mei_io_cb_free(9), mei_tx_cb_enqueue(9), mei_tx_cb_dequeue(9), mei_cl_set_read_by_fp(9), mei_io_cb_init(9), mei_io_tx_list_free_cl(9), mei_io_rd_list_free_fp(9), mei_cl_free_pending(9), mei_cl_alloc_cb(9), mei_cl_enqueue_ctrl_wr_cb(9), mei_cl_read_cb(9), mei_cl_flush_queues(9), mei_cl_init(9), mei_cl_allocate(9), mei_cl_link(9), mei_cl_unlink(9), mei_hbuf_acquire(9), mei_cl_wake_all(9), mei_cl_set_disconnected(9), mei_cl_irq_disconnect(9), __mei_cl_disconnect(9), mei_cl_disconnect(9), mei_cl_is_other_connecting(9), mei_cl_send_connect(9), mei_cl_irq_connect(9), mei_cl_connect(9), mei_cl_alloc_linked(9), mei_cl_tx_flow_ctrl_creds(9), mei_cl_tx_flow_ctrl_creds_reduce(9), mei_cl_vtag_alloc(9), mei_cl_fp_by_vtag(9), mei_cl_reset_read_by_vtag(9), mei_cl_read_vtag_add_fc(9), mei_cl_vt_support_check(9), mei_cl_add_rd_completed(9), mei_cl_del_rd_completed(9), mei_cl_notify_fop2req(9), mei_cl_notify_req2fop(9), mei_cl_irq_notify(9), mei_cl_notify_request(9), mei_cl_notify(9), mei_cl_notify_get(9), mei_cl_read_start(9), mei_msg_hdr_init(9), mei_cl_irq_write(9), mei_cl_write(9), mei_cl_complete(9), mei_cl_all_disconnect(9), mei_cl_irq_dma_map(9), mei_cl_irq_dma_unmap(9), mei_cl_dma_alloc_and_map(9), mei_cl_dma_unmap(9)

like I said. a lot of friends. every single one of them is listed, go say hi πŸ’–


ngl if you're looking for options or flags or env vars or exit codes β€” there are none here. this is a plain kernel function, not a command. no settings, no config, no vibes to tune. just head, cl, and out. πŸ”₯

okay that's the whole page bestie, you ate that 🫢 this one's from the ./drivers/misc/mei source tree, dated October 2026 β€” see you in the next manpage, mwah πŸ’œπŸŽ€β­

πŸ“¦ where this page comes from