linux-kernel - linux-next: manual merge of the spi-fixes tree with Linus' 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: <20210920084408.4c93f5a1@canb.auug.org.au>
Date:   Mon, 20 Sep 2021 08:44:08 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Mark Brown <broonie@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Guenter Roeck <linux@...ck-us.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the spi-fixes tree with Linus' tree

Hi all,

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

  drivers/spi/spi-tegra20-slink.c

between commit:

  efafec27c565 ("spi: Fix tegra20 build with CONFIG_PM=n")

from the origin tree and commit:

  2bab94090b01 ("spi: tegra20-slink: Declare runtime suspend and resume functions conditionally")

from the spi-fixes tree.

I fixed it up (I just used the letter version as that has been in
linux-next for 10 days already) 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.

Mark, maybe fixes need to move on to Linus a bit faster?

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped