linux-kernel - linux-next: manual merge of the spi tree with the hwmon-staging 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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220210132506.051144fb@canb.auug.org.au>
Date:   Thu, 10 Feb 2022 13:25:06 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Mark Brown <broonie@...nel.org>, Guenter Roeck <linux@...ck-us.net>
Cc:     Cosmin Tanislav <cosmin.tanislav@...log.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>
Subject: linux-next: manual merge of the spi tree with the hwmon-staging
 tree

Hi all,

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

  drivers/hwmon/adt7310.c

between commits:

  9c950b125f78 ("hwmon: (adt7x10) Remove empty driver removal callback")

from the hwmon-staging tree and commit:

  a0386bba7093 ("spi: make remove callback a void function")

from the spi tree.

I fixed it up (I just used the former version) 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