devl_health_...rter_destroy(9)

💅 devl_health_...rter_destroy(9) — like, the whole vibe ✨

okay so bestie, welcome to the Kernel API Manual 🎀 — yes that's the manual name, that's where we live now. This page is all about devl_health_...rter_destroy(9) (the header goes by that name, we're just being cute about it 🫶) and honestly? It's a short one. A little destroyer. A lil guy. Let's get into it 💖

---

🌸 NAME 🌸

devl_health_reporter_destroy — destroy devlink health reporter 💀✨

Like literally, it destroys it. The name is not being mysterious. She's an icon, she tells you exactly what she does.

---

🦋 SYNOPSIS 🦋

void devl_health_reporter_destroy (struct devlink_health_reporter
*reporter );

the way that void is just sitting there telling you she returns nothing. no notes. no return value. no drama. periodt 💅

---

🎀 ARGUMENTS 🎀

• reporter — the devlink health reporter to destroy 💀 that's it, that's the whole argument. she's the main character of this function and her only job is to get destroyed. rip bestie 🕊️

---

🔥 SEE ALSO 🔥

• Kernel file ./net/devlink/health.c 👑 — the actual source file, go read her, she's iconic
• devl_port_health_reporter_create(9) 🌈
• devl_health_reporter_create(9) ⭐
• devlink_fmsg_dump_skb(9) 🍓

like yeah, the create functions being listed right next to the destroy one? it's giving balance. it's giving duality. iykyk 🧚

---

ngl bestie, this page is short but she's complete — no extra flags, no hidden options, no environment variables, nothing lurking. what you see is what you get, fr fr 💜

---

and that's the page!! sourced from ./net/devlink and dated October 2026 — so go forth, destroy your health reporters responsibly, and remember: void means no return value and no cap 💖✨🫶