[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250428142452.64ff7dd7@canb.auug.org.au>
Date: Mon, 28 Apr 2025 14:24:52 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Dave Airlie <airlied@...hat.com>, DRI <dri-devel@...ts.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
Mailing List <linux-next@...r.kernel.org>, Lucas De Marchi
<lucas.demarchi@...el.com>, Thomas Hellström
<thomas.hellstrom@...ux.intel.com>, DRM XE List
<intel-xe@...ts.freedesktop.org>
Subject: Re: linux-next: build failure after merge of the drm tree
Hi all,
On Mon, 28 Apr 2025 13:30:13 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> In file included from drivers/gpu/drm/xe/xe_bo.c:3118:
> drivers/gpu/drm/xe/tests/xe_bo.c: In function 'ccs_test_migrate':
> drivers/gpu/drm/xe/tests/xe_bo.c:63:15: error: too many arguments to function 'xe_bo_evict'
> 63 | ret = xe_bo_evict(bo, true);
> | ^~~~~~~~~~~
> drivers/gpu/drm/xe/xe_bo.c:2939:5: note: declared here
> 2939 | int xe_bo_evict(struct xe_bo *bo)
> | ^~~~~~~~~~~
>
> Caused by commit
>
> 55df7c0c62c1 ("drm/ttm/xe: drop unused force_alloc flag")
>
> I have used the drm tree from next-20250424 for today.
The fix for this turned up in the drm-xe tree while I was writing the
above. I have now used the current drm tree combined with the current
drm-xe tree for today. So the drm tree on its own is broken as above,
but linux-next is not.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists