mc_remove(9)

💖 mc_remove(9) 💖

okay so this is a page straight out of the Kernel API Manual bestie, and it's a tiny one — like, one-function tiny — but we're gonna give it the full main character treatment anyway 🎀

---

✨ NAME ✨

mc_remove — the one whose whole job is unbinding a driver from its controller. that's it. that's the gig 💅

---

🌸 SYNOPSIS 🌸

void mc_remove (struct platform_device *pdev );

like, that's the entire call. no int return, no flags, no drama. just vibes and a void 🦋

---

🫶 ARGUMENTS 🫶

• pdev — the platform device. yes, the platform device. that's the whole description, she's lowkey mysterious like that 🙈

---

⭐ RETURN ⭐

Unconditionally 0. not "0 on success, negative on error" — unconditionally. it always comes back 0, no cap. the girl has never known failure and honestly? iconic 👑

---

🔥 SEE ALSO 🔥

the whole friend group 🫶 — first up, the kernel file this lives in:

• ./drivers/edac/synopsys_edac.c

and then the crew, in exactly this order:

• struct ecc_error_info(9)
• struct synps_ecc_status(9)
• struct synps_edac_priv(9)
• struct synps_platform_data(9)
• zynq_get_error_info(9)
• zynqmp_get_mem_info(9)
• zynqmp_get_error_info(9)
• handle_error(9)
• intr_handler(9)
• check_errors(9)
• zynq_get_dtype(9)
• zynqmp_get_dtype(9)
• get_memsize(9)
• zynq_get_mtype(9)
• zynqmp_get_mtype(9)
• init_csrows(9)
• mc_init(9)
• ddr_poison_setup(9)
• setup_address_map(9)
• mc_probe(9)

go read mc_probe(9) next if you wanna see the before of this whole situation — the probe/remove pipeline is giving matched set energy 💜

---

and that's the page!! short, sweet, void, returns 0, done. this lil number ships from ./drivers/edac and it's dated October 2026, so go forth and unbind responsibly, bestie 🌈💖✨