STRUCT ETHNL_REPLY_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct ethnl_reply_data(9)

okay so bestie, welcome to the Kernel API Manual ✨ β€” we're talking about the struct ethnl_reply_data today, and honestly? it's giving lowkey essential. it's the base type of reply data for GET requests 🫢


🌸 NAME 🌸

struct ethnl_reply_data β€” the base type of reply data for GET requests, no cap πŸ’–


✨ SYNOPSIS ✨

struct ethnl_reply_data {
    struct net_device               *dev;
};

look at her. one member. iconic. minimalist queen πŸ‘‘


πŸ¦‹ Members πŸ¦‹

  • dev β€” this is the device for the current reply message πŸ”₯ and here's the tea: in single shot requests it is equal to ethnl_req_info.dev; but in dumps it's different for each reply message πŸ‘€ so like, don't assume, mkay?

πŸŽ€ Description πŸŽ€

So this struct is the common base for request specific structures that hold data for a kernel reply message πŸ’« These always embed struct ethnl_reply_data at zero offset β€” yes bestie, zero offset, that's the whole vibe 🧚


🌈 SEE ALSO 🌈

like, go read all of those too, they're literally all connected πŸ’œ


and that's the whole page bestie!! this came straight out of ./net/ethtool and it's dated October 2026 β€” so yes, we're being very future-forward here ⭐ slay, bye!! πŸ’…πŸ’–

πŸ“¦ where this page comes from