dm_test_add_...ppends_value(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

ok so dm_test_add_modifier_appends_value — it's the kernel-API test that verifies one modifier append, bestie. that's the whole vibe. we're checking a modifier actually got appended and the size got updated, no cap 💖

this one lives in the dm_test_add_...ppends_value(9) manual page, section 9 (kernel API), in case you were wondering where you wandered into 🧚

✨ SYNOPSIS ✨

void dm_test_add_modifier_appends_value (struct kunit *test );

that's it. that's the signature. she's simple, she's iconic, she takes exactly one thing 👑

🎀 ARGUMENTS 🎀

  • test — the KUnit test context. that's the whole parameter list, one (1) argument, and it's just the test harness handing you the context so you can do your thing 🫶

🌸 DESCRIPTION 🌸

okay so picture this: we're verifying if a modifier is appended and size is updated. that's the entire job. the test adds a modifier, then checks that yeah, it actually got appended — and that the size got updated along with it. literally the vibe check for modifier-appending 💅✨

like, either the modifier is in there and the size reflects it, or the test has opinions. no in-between, periodt 🔥

🦋 SEE ALSO 🦋

the kernel file in question, obviously:

  • ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_plane_test.c

and now, the entire friend group — every single sibling test, zero skipped, we do not leave anyone out 🙈💜:

ok and before you go — the boring-but-important receipts 📜: this page comes from ./drivers/gpu/drm/amd/display/..., dated October 2026. that's the source and the date, mentioned here cute-style instead of stapled to the bottom of your terminal. slay 💅✨ keep it in your back pocket, iykyk 🍓💜
📦 where this page comes from