| 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
| ||
|
Message-ID: <20250611120801.48566070@canb.auug.org.au>
Date: Wed, 11 Jun 2025 12:08:01 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Simona Vetter <simona.vetter@...ll.ch>
Cc: Intel Graphics <intel-gfx@...ts.freedesktop.org>, DRI
<dri-devel@...ts.freedesktop.org>, Dmitry Baryshkov
<dmitry.baryshkov@...aro.org>, Dmitry Baryshkov
<dmitry.baryshkov@....qualcomm.com>, Gabriel Dalimonte
<gabriel.dalimonte@...il.com>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Maxime Ripard <mripard@...nel.org>
Subject: linux-next: manual merge of the drm-misc tree with the
drm-misc-fixes tree
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/vc4/vc4_hdmi.c
between commit:
c0317ad44f45 ("drm/vc4: fix infinite EPROBE_DEFER loop")
from the drm-misc-fixes tree and commit:
d9f9bae6752f ("drm/bridge: allow limiting I2S formats")
from the drm-misc tree.
I fixed it up (the former removes code updated by the latter, so I just
removed the code) 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.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists