From: Srinivas Kandagatla <srinivas.kandagatla@linaro•org>
To: Miquel Raynal <miquel.raynal@bootlin•com>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: 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, 11 Dec 2023 11:09:27 +0000 [thread overview]
Message-ID: <dfc3d1f8-79fe-494d-a946-0e317d36d51c@linaro.org> (raw)
In-Reply-To: <20231211113419.327947a7@xps-13>
On 11/12/2023 10:34, Miquel Raynal wrote:
> Hi Stephen,
>
> sfr@canb•auug.org.au wrote on Mon, 11 Dec 2023 08:48:41 +1100:
>
>> Hi all,
>>
>> The following commit is also in Linus Torvalds' tree as a different commit
>> (but the same patch):
>>
>> 05349b48e254 ("nvmem: Do not expect fixed layouts to grab a layout driver")
>>
>> This is commit
>>
>> b7c1e53751cb ("nvmem: Do not expect fixed layouts to grab a layout driver")
>>
>> in Linus' tree.
>>
>> Also, please keep all the commit message tags together at the end of
>> the commit message.
>>
>
> This is actually fine, Srinivas needs this fix in his tree for
> applying other patches, but he anyway sends a big "series" to GKH at
> -rc6 who finally applies the content of the nvmem-next branch.
Or I can merge or rebase on rc5 which should ensure that there are no
duplicates.
--srini
>
> Thanks for the reports,
> Miquèl
next prev parent reply other threads:[~2023-12-11 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 21:48 linux-next: duplicate patch in the nvmem tree Stephen Rothwell
2023-12-11 10:34 ` Miquel Raynal
2023-12-11 11:09 ` Srinivas Kandagatla [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
2025-07-14 7:34 Stephen Rothwell
2025-07-14 7:51 ` Greg KH
2024-06-12 6:28 Stephen Rothwell
2024-06-12 12:55 ` Rob Herring
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=dfc3d1f8-79fe-494d-a946-0e317d36d51c@linaro.org \
--to=srinivas.kandagatla@linaro$(echo .)org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miquel.raynal@bootlin$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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