STRUCT MOST_COMPONENT(9)

💖 NAME 💖

okay so bestie, this is from the Kernel API Manual (section 9, obvi ✨), and we're talking about struct most_component — it literally identifies a loadable component for the mostcore. That's the whole vibe. 💅

🌸 SYNOPSIS 🌸

here's the struct in all its glory, exactly as it appears, no cap:

       struct most_component {
           struct list_head list;
           const char *name;
           struct module *mod;
           int (*probe_channel)(struct most_interface *iface, int channel_idx,
       struct most_channel_config *cfg, char *name, char *param);
           int (*disconnect_channel)(struct most_interface *iface, int
       channel_idx);
           int (*rx_completion)(struct mbo *mbo);
           int (*tx_completion)(struct most_interface *iface, int channel_idx);
           int (*cfg_complete)(void);
        };

🦋 Members 🦋

• list — list_head. iconic little list field, periodt 🎀
• name — component name. yes bestie, it has a name 💖
• mod — owning module. the module that owns it, slay 👑
• probe_channel — function for core to notify driver about channel connection.
• disconnect_channel — callback function to disconnect a certain channel.
• rx_completion — completion handler for received packets.
• tx_completion — completion handler for transmitted packets.
• cfg_complete — setup completion function called after the device is matched.

🌈 SEE ALSO 🌈

Kernel file ./include/linux — plus these absolute legends, go read them bestie:

• enum most_interface_type(9)
• enum most_channel_direction(9)
• enum most_channel_data_type(9)
• struct most_channel_capability(9)
• struct most_channel_config(9)
• struct most_interface(9)
• most_register_interface(9)
• most_deregister_interface(9)
• most_stop_enqueue(9)
• most_resume_enqueue(9)

mwah 💋 this page's source is ./include/linux, its date is October 2026, and it's literally titled struct most_component(9). bye bestie 🫶✨