ufs_mtk_remove(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ufs_mtk_remove(9) β€” the kernel API manual, but make it cute

okay so bestie, welcome to ufs_mtk_remove(9), a tiny little kernel function that has ONE job and honestly? she does it. this page lives in the Kernel API Manual and it's short enough to read while your build finishes, so let's go 🫢


✨ NAME ✨

ufs_mtk_remove β€” set driver_data of the device to NULL

that's it. that's the whole personality. she cleans up the driver_data pointer and sets it to NULL, and the way that's literally her entire name section is iconic honestly πŸ’…


🌸 SYNOPSIS 🌸

void ufs_mtk_remove (struct platform_device *pdev );

look at her. no return value, one argument. main character energy with zero drama πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • pdev β€” pointer to the platform device handle πŸ¦‹ that's the thing you're handing over, the platform device handle itself, passed by pointer. give her the device, she'll handle the rest.

πŸ’– DESCRIPTION πŸ’–

so what does she actually do? she sets driver_data of the device to NULL. that's the gig. that's the whole gig.

and then β€” and this is the part that sends me 😭 β€” the page says she always return 0. literally always. "Always return 0." no conditions, no "unless", no asterisk, no fine print. yes, the signature up in SYNOPSIS is void, and yes, the page still says "Always return 0" β€” I'm just the messenger, bestie, I'm not out here rewriting kernel semantics, that's above my pay grade πŸ’€ take it as written, no cap.


πŸ¦‹ SEE ALSO πŸ¦‹

the whole mediatek UFS host squad, all linked up, all worth a read β€” probe and remove are literally sisters, you gotta meet both 🧚


lowkey a reminder: this page is about ufs_mtk_remove only β€” everything it does is set driver_data of the device to NULL, and per the manual it "Always return 0". nothing extra, nothing invented, and honestly that's the vibe check she passed 🌈

kisses bestie, that's the page πŸ’œ this little beauty comes from ./drivers/ufs/host and is dated October 2026 β€” go forth, remove devices, set that driver_data to NULL, and slay βœ¨πŸŽ€πŸ’…

πŸ“¦ where this page comes from