kunit_platform_device_alloc(9)

✨ kunit_platform_device_alloc(9) ✨

okay so bestie, this one's from the Kernel API Manual — it's the kunit_platform_device_alloc page, and honestly it's giving "tiny function, big responsibilities" energy 💅

---

🌸 NAME 🌸

kunit_platform_device_alloc — allocate a KUnit test managed platform device 🎀

🦋 SYNOPSIS 🦋

struct platform_device * kunit_platform_device_alloc (struct kunit *test
, const char *name , int id );

💖 ARGUMENTS 💖

• test — the test context, like the group chat this whole operation lives in 🫶
• name — the device name of the platform device you're alloc-ing, iykyk
• id — the identifier of the platform device you're alloc-ing.

🌈 DESCRIPTION 🌈

So you allocate a test managed platform device ✨ and the best part? The device gets put automatically when the test completes. Literally self-cleaning, main character energy 🔥 no cap.

⭐ RETURN ⭐

• Allocated platform device on success 👑
• NULL on failure 💀

🧚 SEE ALSO 🧚

• Kernel file ./lib/kunit/platform.c
• kunit_platform_device_add(9)
• kunit_platform_device_register_full(9)
• kunit_platform_device_unregister(9)
• kunit_platform_device_prepare_wait_for_probe(9)
• kunit_platform_driver_register(9)

---

and that's the whole page, bestie — go forth and allocate responsibly 💜

this cutie lives in ./lib/kunit and the page is dated October 2026 🌸 so yeah, it's basically from the future fr fr 🦋💫

mwah, go slay some kernel tests 💅✨🎀