Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8;
Message-ID: <02ce70da-346b-6c24-b7ed-8f5b30f1c99b@linaro.org>
Date:   Tue, 17 Oct 2023 06:45:19 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.15.1
Subject: Re: linux-next: duplicate patches in the nvmem tree
Content-Language: en-US
To:     Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
        Arnd Bergmann <arnd@arndb.de>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20231017150714.41a6c640@canb.auug.org.au>
From:   Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
In-Reply-To: <20231017150714.41a6c640@canb.auug.org.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.
>