From: "Rafał Miłecki" <rafal@milecki.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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, 30 Oct 2023 07:46:36 +0100 [thread overview]
Message-ID: <3237d305e6b61a8113771ce0b9151867@milecki.pl> (raw)
In-Reply-To: <20231030151024.35d0910c@canb.auug.org.au>
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
next prev parent reply other threads:[~2023-10-30 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 4:10 linux-next: duplicate patch in the nvmem tree Stephen Rothwell
2023-10-30 6:46 ` Rafał Miłecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-10 21:48 Stephen Rothwell
2023-12-11 10:34 ` Miquel Raynal
2023-12-11 11:09 ` Srinivas Kandagatla
2024-06-12 6:28 Stephen Rothwell
2024-06-12 12:55 ` Rob Herring
2025-07-14 7:34 Stephen Rothwell
2025-07-14 7:51 ` Greg KH
2025-11-25 6:17 Stephen Rothwell
2025-11-25 7:10 ` Greg KH
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=3237d305e6b61a8113771ce0b9151867@milecki.pl \
--to=rafal@milecki.pl \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=srinivas.kandagatla@linaro.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