linux-kernel - Re: linux-next: duplicate patch in the nvmem 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231211113419.327947a7@xps-13>
Date:   Mon, 11 Dec 2023 11:34:19 +0100
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the nvmem tree

Hi Stephen,

sfr@...b.auug.org.au wrote on Mon, 11 Dec 2023 08:48:41 +1100:

> Hi all,
> 
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
> 
>   05349b48e254 ("nvmem: Do not expect fixed layouts to grab a layout driver")
> 
> This is commit
> 
>   b7c1e53751cb ("nvmem: Do not expect fixed layouts to grab a layout driver")
> 
> in Linus' tree.
> 
> Also, please keep all the commit message tags together at the end of
> the commit message.
> 

This is actually fine, Srinivas needs this fix in his tree for
applying other patches, but he anyway sends a big "series" to GKH at
-rc6 who finally applies the content of the nvmem-next branch.

Thanks for the reports,
Miquèl