From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the nvmem tree
Date: Mon, 14 Jul 2025 09:51:10 +0200 [thread overview]
Message-ID: <2025071443-humbling-paddling-a4de@gregkh> (raw)
In-Reply-To: <20250714173446.7e78d9cf@canb.auug.org.au>
On Mon, Jul 14, 2025 at 05:34:46PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the char-misc.current tree as a different
> commit (but the same patch):
>
> d102a7924f44 ("nvmem: imx-ocotp: fix MAC address byte length")
>
> This is commit
>
> 2aa4ad626ee7 ("nvmem: imx-ocotp: fix MAC address byte length")
>
> in the char-misc.current tree.
That's due to the nvmem tree sending them to me in patch format. Should
be fine, thanks!
greg k-h
next prev parent reply other threads:[~2025-07-14 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 7:34 linux-next: duplicate patch in the nvmem tree Stephen Rothwell
2025-07-14 7:51 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-25 6:17 Stephen Rothwell
2025-11-25 7:10 ` Greg KH
2024-06-12 6:28 Stephen Rothwell
2024-06-12 12:55 ` Rob Herring
2023-12-10 21:48 Stephen Rothwell
2023-12-11 10:34 ` Miquel Raynal
2023-12-11 11:09 ` Srinivas Kandagatla
2023-10-30 4:10 Stephen Rothwell
2023-10-30 6:46 ` Rafał Miłecki
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=2025071443-humbling-paddling-a4de@gregkh \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=srini@kernel.org \
/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