devlink_rem...ns_performed(9)

💅 devlink_remote_reload_actions_performed(9)

okay bestie, so this is a page from the Kernel API Manual and it's literally all about devlink_remote_reload_actions_performed — say that five times fast, i dare you 🫶 don't worry, it's way less scary than it looks.

---

✨ NAME ✨

devlink_remote_reload_actions_performed — update devlink on reload actions performed that are not a direct result of a devlink reload call. like, the drama happened somewhere else and devlink still needs to know about it, yk? 💅

---

🌸 SYNOPSIS 🌸

void devlink_remote_reload_actions_performed (struct devlink *devlink ,
       enum devlink_reload_limit limit , u32 actions_performed );

she's a void function, she takes three args, she slays. periodt. 🎀

---

🦋 ARGUMENTS 🦋

• devlink — it's the devlink. that's the whole vibe. 💖
• limit — the reload limit, of the enum devlink_reload_limit variety.
• actions_performed — a bitmask of the actions that were performed. bitmask, bestie, so it's bit-flavoured. 🔥

---

👑 DESCRIPTION 👑

okay so here's the tea ☕ — a driver should call this after it performs reload actions, but only in the case where those actions were not a result of a devlink reload call. like, the reload was giving side quest, not main character energy.

for example: fw_activate was performed as a result of a devlink reload that was triggered by fw_activate on another host. yes, another host. remote drama. 🌈

the motivation for this function is to keep data on reload actions performed on this function — whether it was done due to a direct devlink reload call or not. so like, the records stay cute and complete no matter who started it. iykyk 💀

---

🔍 SEE ALSO 🔍

• Kernel file ./net/devlink/dev.c — go read it, it's giving source of truth ✨

---

and that's the whole page, bestie!! no cap, you ate that 🍓 this lil gem lives in ./net/devlink, dated October 2026, and she's proudly known as devlink_rem...ns_performed(9) — truncated name and all, we stan a mysterious queen 💜🧚