STRUCT MEI_CONNECT_CLIENT_DATA_VTAG(9)
π NAME π
okay bestie, this page is from the Kernel API Manual, and the cover title is struct mei_...nt_data_vtag(9) β¨. The NAME line is literally struct mei_connect_client_data_vtag - IOCTL connect data union, and that's the whole vibe: it's the IOCTL connect data union π
. No cap.
πΈ SYNOPSIS πΈ
Here's the struct in all her glory β code stays character-for-character, obviously:
struct mei_connect_client_data_vtag {
union {
struct mei_connect_client_vtag connect;
struct mei_client out_client_properties;
};
};
π«Ά Members π«Ά
{unnamed_union}β anonymous. She's mysterious, she has no name, and honestly? Iconic. πconnectβ the input connect data. That's what goes in.out_client_propertiesβ the output client data. That's what comes back out.
π SEE ALSO π
- Kernel file
./include/uapi/linux/mei.hset and unset event notification for a connected client(9) - retrieve notification(9)
struct mei_connect_client_vtag(9)- Introduction(9)
okay that's the whole page, bestie π this one's sourced from./include/uapi/linux, dated October 2026, and the page isstruct mei_...nt_data_vtag(9)β mwah, bye! πβ¨
π¦ 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