From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
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>
Subject: Re: linux-next: duplicate patches in the nvmem tree
Date: Tue, 17 Oct 2023 06:45:19 +0100 [thread overview]
Message-ID: <02ce70da-346b-6c24-b7ed-8f5b30f1c99b@linaro.org> (raw)
In-Reply-To: <20231017150714.41a6c640@canb.auug.org.au>
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.
>
next prev parent reply other threads:[~2023-10-17 5:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 4:07 linux-next: duplicate patches in the nvmem tree Stephen Rothwell
2023-10-17 5:45 ` Srinivas Kandagatla [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 5:42 Stephen Rothwell
2023-12-18 5:12 Stephen Rothwell
2023-12-18 10:26 ` Greg KH
2023-12-18 10:38 ` Srinivas Kandagatla
2023-12-18 10:30 ` Srinivas Kandagatla
2023-10-25 4:23 Stephen Rothwell
2023-09-25 22:34 Stephen Rothwell
2023-09-26 6:03 ` Srinivas Kandagatla
2023-09-04 22:04 Stephen Rothwell
2023-07-03 21:58 Stephen Rothwell
2023-05-08 1:00 Stephen Rothwell
2023-02-05 21:32 Stephen Rothwell
2023-03-05 23:51 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02ce70da-346b-6c24-b7ed-8f5b30f1c99b@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).