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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 30 Oct 2023 07:46:36 +0100
From:   Rafał Miłecki <rafal@...ecki.pl>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Greg KH <greg@...ah.com>, Arnd Bergmann <arnd@...db.de>,
        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,

On 2023-10-30 05:10, Stephen Rothwell wrote:
> The following commit is also in char-misc tree as a different commit
> (but the same patch):
> 
>   ca7384334d9b ("Revert "nvmem: add new config option"")
> 
> This is commit
> 
>   f4cf4e5db331 ("Revert "nvmem: add new config option"")
> 
> in the char-misc tree.

please ignore patch in nvmem.git, it's an old version applied on top of
outdated code.

Code in char-misc.git which is meant to go to Linus is all good, we're
all safe :)

-- 
Rafał Miłecki