ethnl_init_reply_data(9)

💅 ethnl_init_reply_data(9) 💅

okay so bestie, this one is straight from the Kernel API Manual, and it's giving “prep the reply data before the GET request” main character energy. no cap. ✨

---

🌸 NAME 🌸

ethnl_init_reply_data — Initialize reply data for GET request. slay.

---

✨ SYNOPSIS ✨

void ethnl_init_reply_data (struct ethnl_reply_data *reply_data , const
struct ethnl_request_ops *ops , struct net_device *dev );

---

🎀 ARGUMENTS 🎀

• reply_data — pointer to embedded struct ethnl_reply_data. yes, embedded, bestie.
• ops — instance of struct ethnl_request_ops describing the layout. it's the blueprint vibes.
• dev — network device to initialize the reply for. the device in question, periodt.

---

🦋 DESCRIPTION 🦋

Fills the reply data part with zeros and sets the dev member. Must be called before calling the ->fill_reply callback (for each iteration when handling dump requests).

That's the whole vibe: zero it out, set dev, and do it before ->fill_reply. For dump requests, this is each iteration. don't skip it, fr fr.

---

🔥 SEE ALSO 🔥

Kernel file ./net/ethtool/netlink.c, plus these iconic little references:

• ethnl_parse_header_dev_get(9)
• ethnl_fill_reply_header(9)
• ethnl_reply_init(9)
• struct ethnl_dump_ctx(9)
• struct ethnl_perphy_dump_ctx(9)
• ethnl_default_parse(9)

---

mwah 💋 source/version ./net/ethtool, date October 2026, and this page is ethnl_init_reply_data(9) from the Kernel API Manual. 🫶