✗ CI.checkpatch: warning for drm/tests/gpu_buddy: fix interleaving in buffer clearance test (rev2)
Patchwork <[email protected]> Mon, 03 Aug 2026 11:54:28 -0000
| Newsgroups | org.freedesktop.lists.intel-xe |
|---|---|
| Message-ID | <178575806822.13594.3407051861149480320@61270ab9df2a> |
== Series Details == Series: drm/tests/gpu_buddy: fix interleaving in buffer clearance test (rev2) URL : https://patchwork.freedesktop.org/series/170880/ State : warning == Summary == + KERNEL=/kernel + git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt Cloning into 'mt'... warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/ + git -C mt rev-list -n1 origin/master 061140b9bc586ae7f40abc1249c97e1cc72d1b9d + cd /kernel + git config --global --add safe.directory /kernel + git log -n1 commit e1999fb2e1afafb907c63d0a40a02c8db3e2d540 Author: Arunpravin Paneer Selvam <[email protected]> Date: Mon Aug 3 12:26:56 2026 +0530 drm/tests/gpu_buddy: fix interleaving in buffer clearance test The resume clearance test skipped every other allocation, expecting an interleaved clear/dirty layout. But the buddy allocator hands out blocks contiguously, so this just allocated half the pages in one chunk and never exercised gpu_buddy_reset_clear()'s force-merge of opposite-state buddies. Allocate all pages into two lists instead and free one cleared, one dirty, to build a truly interleaved pattern. v2: Use for loops instead of do-while for the allocation loops (Jani Nikula) Fixes: e3335ccbf4da ("drm/tests/gpu_buddy: add a new test case for buffer clearance during resume") Reported-by: Sashiko-bot <[email protected]> Closes: https://sashiko.dev/#/patchset/[email protected]?part=1 Cc: Matthew Auld <[email protected]> Cc: Christian König <[email protected]> Assisted-by: GitHub_Copilot:claude-opus-4.8 Signed-off-by: Arunpravin Paneer Selvam <[email protected]> + /mt/dim checkpatch f8d080b47819f01011c1b9c3c875badbb67ec955 drm-intel e1999fb2e1af drm/tests/gpu_buddy: fix interleaving in buffer clearance test -:17: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?) #17: v2: Use for loops instead of do-while for the allocation loops (Jani Nikula) total: 0 errors, 1 warnings, 0 checks, 75 lines checked