of_overlay_fdt_apply_kunit(9)

💖 of_overlay_fdt_apply_kunit(9) 💖

okay bestie, you're looking at the Kernel API Manual page for of_overlay_fdt_apply_kunit — the KUnit helper that's literally "test-managed overlay" coded. ✨

🌸 NAME 🌸

of_overlay_fdt_apply_kunit — Test managed of_overlay_fdt_apply()

🎀 SYNOPSIS 🎀

int of_overlay_fdt_apply_kunit (struct kunit *test , void *overlay_fdt ,
       u32 overlay_fdt_size , int *ovcs_id );

🦋 ARGUMENTS 🦋

• test — test context. it's the test's own little context bubble, the vibe check for the test itself 💅
• overlay_fdt — device tree overlay to apply. the actual overlay bestie, no cap 🌈
• overlay_fdt_size — size in bytes of overlay_fdt. bytes, not vibes, okay? 🍓
• ovcs_id — identifier of overlay, used to remove the overlay. keep it around for cleanup time 🧹

✨ DESCRIPTION ✨

Literally just like of_overlay_fdt_apply, except the overlay is managed by the test case and is automatically removed with of_overlay_remove after the test case concludes. the test case handles teardown, you just vibe 🫶

🔥 RETURN 🔥

• 0 on success, negative errno on failure 😭

👑 SEE ALSO 👑

• Kernel file ./drivers/of/of_kunit_helpers.c
• of_root_kunit_skip(9)
• of_node_put_kunit(9)

made with 💜 from ./drivers/of · October 2026 — slay, bestie, go test those overlays 🎀