linux-kernel - Re: linux-next: duplicate patches 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] [day] [month] [year] [list]

Message-ID: <02ce70da-346b-6c24-b7ed-8f5b30f1c99b@linaro.org>
Date:   Tue, 17 Oct 2023 06:45:19 +0100
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>, Greg KH <greg@...ah.com>,
        Arnd Bergmann <arnd@...db.de>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the nvmem tree

Thanks Stephen,

This is now fixed for both nvmem and fastrpc tree.

--srini
On 17/10/2023 05:07, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in the char-misc.current tree as different
> commits (but the same patches):
> 
>    d0b450caca6f ("nvmem: imx: correct nregs for i.MX6ULL")
>    f46cfdaf5c07 ("nvmem: imx: correct nregs for i.MX6UL")
>    e898831a6683 ("nvmem: imx: correct nregs for i.MX6SLL")
> 
> These are commits
> 
>    2382c1b04423 ("nvmem: imx: correct nregs for i.MX6ULL")
>    7d6e10f5d254 ("nvmem: imx: correct nregs for i.MX6UL")
>    414a98abbefd ("nvmem: imx: correct nregs for i.MX6SLL")
> 
> in the char-misc.current tree.
>