ethnl_reply_init(9)

✨ ethnl_reply_init(9) ✨

okay bestie, so this is a page straight out of the Kernel API Manual — we're talking ethnl_reply_init, and it's lowkey the moment a reply gets its whole life together 💅

---

🌸 NAME 🌸

ethnl_reply_init — create the skb for a reply and fill in the device identification 🎀

---

🦋 SYNOPSIS 🦋

struct sk_buff * ethnl_reply_init (size_t payload , struct net_device
*dev , u8 cmd , u16 hdr_attrtype , struct genl_info *info , void **ehdrp
);

---

💖 ARGUMENTS 💖

• payload — the payload length, and no cap, this is without the netlink and genetlink header 🫶
• dev — the device this reply is all about (it may be null, and that's fine, we don't judge 🙈)
• cmd — the ETHTOOL_MSG_* message type for the reply ⭐
• hdr_attrtype — the attribute type for the common header
• info — the genetlink info of the received packet we're responding to 📥
• ehdrp — the place to store the payload pointer that genlmsg_new returned, iconic little out-param behavior 👑

---

🔥 RETURN 🔥

a pointer to the allocated skb on success, and NULL on error 😭 (yes we hate to see it, but that's the vibe check)

---

🌈 SEE ALSO 🌈

• the Kernel file ./net/ethtool/netlink.c — literally the source, go read it, iykyk 📖
• ethnl_parse_header_dev_get(9)
• ethnl_fill_reply_header(9)
• struct ethnl_dump_ctx(9)
• struct ethnl_perphy_dump_ctx(9)
• ethnl_default_parse(9)
• ethnl_init_reply_data(9)

---

and that's the whole page bestie, no notes 💜 fr fr — this one lives in ./net/ethtool, dated October 2026, and that's the sign-off, mwah 😘🎀🧚