linux-kernel - linux-next: manual merge of the drm-xe tree with the drm-fixes tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <aM1RSLYqXYokkdh-@sirena.org.uk>
Date: Fri, 19 Sep 2025 13:49:12 +0100
From: Mark Brown <broonie@...nel.org>
To: Lucas De Marchi <lucas.demarchi@...el.com>,
	Thomas Hellström <thomas.hellstrom@...ux.intel.com>,
	DRM XE List <intel-xe@...ts.freedesktop.org>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Rodrigo Vivi <rodrigo.vivi@...el.com>
Subject: linux-next: manual merge of the drm-xe tree with the drm-fixes tree

Hi all,

Today's linux-next merge of the drm-xe tree got a conflict in:

  drivers/gpu/drm/xe/xe_guc_submit.c

between commit:

  26caeae9fb482 ("drm/xe/guc: Set RCS/CCS yield policy")

from the drm-fixes tree and commit:

  88434448438e4 ("drm/xe/guc: Set RCS/CCS yield policy")

from the drm-xe 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.

diff --cc drivers/gpu/drm/xe/xe_guc_submit.c
index e377ba3a39b3a,53024eb5670b7..0000000000000
--- a/drivers/gpu/drm/xe/xe_guc_submit.c
+++ b/drivers/gpu/drm/xe/xe_guc_submit.c

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)