From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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, 26 Sep 2023 07:03:09 +0100 [thread overview]
Message-ID: <fc358b53-0ca7-3600-0d27-a5849811ed2c@linaro.org> (raw)
In-Reply-To: <20230926083446.1c3d9914@canb.auug.org.au>
Thanks Stephen for reporting this.
Its fixed now.
--srini
On 25/09/2023 23:34, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> 0991afbe4b18 ("nvmem: core: Notify when a new layout is registered")
> b8257f61b4dd ("nvmem: core: Do not open-code existing functions")
> 6c7f48ea2e66 ("nvmem: core: Return NULL when no nvmem layout is found")
> 104af6a5b199 ("nvmem: core: Create all cells before adding the nvmem device")
> c32f2186acc9 ("nvmem: u-boot-env:: Replace zero-length array with DECLARE_FLEX_ARRAY() helper")
> 0a9ec38c47c1 ("nvmem: sec-qfprom: Add Qualcomm secure QFPROM support")
> 050cd7f49580 ("dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom")
> 4b71b2a44d7d ("dt-bindings: nvmem: Add compatible for QCM2290")
> 9d53d595f688 ("nvmem: Kconfig: Fix typo "drive" -> "driver"")
> 3e0558db94db ("nvmem: Explicitly include correct DT includes")
> c8efcf7a86eb ("nvmem: add new NXP QorIQ eFuse driver")
> 0401edffa338 ("dt-bindings: nvmem: Add t1023-sfp efuse support")
> 8fd85ce6cfdf ("dt-bindings: nvmem: qfprom: Add compatible for MSM8226")
> 97edd4c6ba34 ("nvmem: uniphier: Use devm_platform_get_and_ioremap_resource()")
> 431f08ed0ba5 ("nvmem: qfprom: do some cleanup")
> 77803ef86379 ("nvmem: stm32-romem: Use devm_platform_get_and_ioremap_resource()")
> e75d23cf347d ("nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource()")
> ad065ae27bd1 ("nvmem: meson-mx-efuse: Convert to devm_platform_ioremap_resource()")
> 67f919120705 ("nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource()
> ")
> 5f41033e4154 ("nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource()")
> 6870b4a37343 ("nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource()")
> 31c8217bc34a ("dt-bindings: nvmem: fixed-cell: add compatible for MAC cells")
>
next prev parent reply other threads:[~2023-09-26 6:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 22:34 linux-next: duplicate patches in the nvmem tree Stephen Rothwell
2023-09-26 6:03 ` 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-10-17 4:07 Stephen Rothwell
2023-10-17 5:45 ` 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=fc358b53-0ca7-3600-0d27-a5849811ed2c@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--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).