linux-kernel - linux-next: manual merge of the extcon 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: <Z1MAHZOgRInwoyZi@sirena.org.uk>
Date: Fri, 6 Dec 2024 13:46:05 +0000
From: Mark Brown <broonie@...nel.org>
To: Chanwoo Choi <cw00.choi@...sung.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Uwe Kleine-König <ukleinek@...nel.org>,
	Uwe Kleine-König <u.kleine-koenig@...libre.com>
Subject: linux-next: manual merge of the extcon tree with the origin tree

Hi all,

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

  drivers/extcon/extcon-usbc-cros-ec.c

between commit:

  e70140ba0d2b1 ("Get rid of 'remove_new' relic from platform driver struct")

from the origin tree and commit:

  a5bca5c3931ba ("extcon: Switch back to struct platform_driver::remove()")

from the extcon 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.

(no diff, used Linus' version.)

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