[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250701125705.5d5fb3f0@canb.auug.org.au>
Date: Tue, 1 Jul 2025 12:57:05 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Simona Vetter <simona.vetter@...ll.ch>
Cc: Alex Deucher <alexander.deucher@....com>, Intel Graphics
<intel-gfx@...ts.freedesktop.org>, DRI <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the drm-misc tree with Linus' tree
Hi all,
On Tue, 1 Jul 2025 12:54:43 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Today's linux-next merge of the drm-misc tree got a conflict in:
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
>
> between commit:
>
> ebe43542702c ("drm/amdgpu: switch job hw_fence to amdgpu_fence")
>
> from Linus' tree and commit:
>
> d0c35c84dcfa ("drm/amdgpu: remove job parameter from amdgpu_fence_emit()")
>
> from the drm-misc tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
I used the latter version of the conflicting section.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists