linux-kernel - linux-next: manual merge of the drm tree with the origin 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: <Zn7qE8rGdTMXmhK-@sirena.org.uk>
Date: Fri, 28 Jun 2024 17:51:31 +0100
From: Mark Brown <broonie@...nel.org>
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>,
	Riana Tauro <riana.tauro@...el.com>,
	Rodrigo Vivi <rodrigo.vivi@...el.com>,
	Thomas Hellström <thomas.hellstrom@...ux.intel.com>
Subject: linux-next: manual merge of the drm tree with the origin tree

Hi all,

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

  drivers/gpu/drm/xe/xe_gt_idle.c

between commit:

  2470b141bfae2 ("drm/xe: move disable_c6 call")

from the origin tree and commits:

  6800e63cf97ba ("drm/xe: move disable_c6 call")
  38e8c4184ea0e ("drm/xe: Enable Coarse Power Gating")
  ecab82af27873 ("drm/xe/vf: Don't support gtidle if VF")

from the drm 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_gt_idle.c
index 944770fb2daff,67aba41405100..0000000000000
--- a/drivers/gpu/drm/xe/xe_gt_idle.c
+++ b/drivers/gpu/drm/xe/xe_gt_idle.c

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