public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 patches in the nvmem tree
Date: Tue, 5 Nov 2024 11:21:07 +0000	[thread overview]
Message-ID: <5d2af7fa-f697-4ecc-a341-68713b1594e2@linaro.org> (raw)
In-Reply-To: <2024110546-muppet-flashback-2e2d@gregkh>



On 05/11/2024 09:46, Greg KH wrote:
> On Tue, Nov 05, 2024 at 04:59:50PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commits are also in the char-misc tree as different commits
>> (but the same patches):
>>
>>    24c50e7003bf ("dt-bindings: nvmem: sprd,ums312-efuse: convert to YAML")
>>    786700e267b0 ("dt-bindings: nvmem: sprd,sc2731-efuse: convert to YAML")
>>    17d6f058403d ("dt-bindings: nvmem: convert zii,rave-sp-eeprom.txt to yaml format")
>>    e2ba37350d1d ("nvmem: imx-iim: Convert comma to semicolon")
>>    3e93f43ae64b ("nvmem: Correct some typos in comments")
>>    5ac5933d4e06 ("nvmem: Add R-Car E-FUSE driver")
>>    149e83f1b385 ("dt-bindings: fuse: Move renesas,rcar-{efuse,otp} to nvmem")
>>
>> These are commits
>>
>>    b8357f6764a2 ("dt-bindings: nvmem: sprd,sc2731-efuse: convert to YAML")
>>    1c4ea801570a ("dt-bindings: nvmem: sprd,ums312-efuse: convert to YAML")
>>    5e61687075e3 ("dt-bindings: nvmem: convert zii,rave-sp-eeprom.txt to yaml format")
>>    2e7bb66b55f4 ("nvmem: imx-iim: Convert comma to semicolon")
>>    b3d75e9ba013 ("nvmem: Correct some typos in comments")
>>    1530b923a514 ("nvmem: Add R-Car E-FUSE driver")
>>    2aea0d17ff9e ("dt-bindings: fuse: Move renesas,rcar-{efuse,otp} to nvmem")
>>
>> in the char-misc tree.
> 
> This is because the nvmem tree sends me patches in email :)
Its fixed now, I will send a PR next time if that works for you.

thanks,
srini

  reply	other threads:[~2024-11-05 11:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  5:59 linux-next: duplicate patches in the nvmem tree Stephen Rothwell
2024-11-05  9:46 ` Greg KH
2024-11-05 11:21   ` Srinivas Kandagatla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-23  6:35 Stephen Rothwell
2024-09-04  6:06 Stephen Rothwell
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-10-17  4:07 Stephen Rothwell
2023-10-17  5:45 ` Srinivas Kandagatla
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=5d2af7fa-f697-4ecc-a341-68713b1594e2@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