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: Mon, 18 Dec 2023 10:38:36 +0000 [thread overview]
Message-ID: <681bfda0-ccc2-4af0-b77e-31c92cf7ada3@linaro.org> (raw)
In-Reply-To: <2023121838-factual-unvalued-3e01@gregkh>
On 18/12/2023 10:26, Greg KH wrote:
> On Mon, Dec 18, 2023 at 04:12:38PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commits are also in Linus Torvalds' tree as different
>> commits (but the same patches):
>>
>> 82c6ba6a7d96 ("nvmem: brcm_nvram: store a copy of NVRAM content")
>> a9d68bd9fc7a ("nvmem: stm32: add support for STM32MP25 BSEC to control OTP data")
>> 5bc8339a8af8 ("dt-bindings: nvmem: add new stm32mp25 compatible for stm32-romem")
>> 6deccfa25e3d ("dt-bindings: nvmem: mxs-ocotp: Document fsl,ocotp")
>> e15e05ed845a ("nvmem: core: Expose cells through sysfs")
>> 38ebc72019b9 ("ABI: sysfs-nvmem-cells: Expose cells through sysfs")
>> fc334e722496 ("nvmem: core: Rework layouts to become regular devices")
>> d5827449f96c ("nvmem: Move and rename ->fixup_cell_info()")
>> 52be3c1543c4 ("nvmem: Simplify the ->add_cells() hook")
>> 26378491d343 ("nvmem: Create a header for internal sharing")
>> c016e72f9346 ("nvmem: Move of_nvmem_layout_get_container() in another header")
>> 0e7ceb1551ee ("of: device: Export of_device_make_bus_id()")
>>
>> These are commits
>>
>> 1e37bf84afac ("nvmem: brcm_nvram: store a copy of NVRAM content")
>> f0ac5b230396 ("nvmem: stm32: add support for STM32MP25 BSEC to control OTP data")
>> a729c0f57dc8 ("dt-bindings: nvmem: add new stm32mp25 compatible for stm32-romem")
>> a2a8aefecbd0 ("dt-bindings: nvmem: mxs-ocotp: Document fsl,ocotp")
>> 0331c611949f ("nvmem: core: Expose cells through sysfs")
>> 192048e5a5b6 ("ABI: sysfs-nvmem-cells: Expose cells through sysfs")
>> fc29fd821d9a ("nvmem: core: Rework layouts to become regular devices")
>> 1172460e7167 ("nvmem: Move and rename ->fixup_cell_info()")
>> 1b7c298a4ecb ("nvmem: Simplify the ->add_cells() hook")
>> ec9c08a1cb8d ("nvmem: Create a header for internal sharing")
>> 4a1a40233b4a ("nvmem: Move of_nvmem_layout_get_container() in another header")
>> 7f38b70042fc ("of: device: Export of_device_make_bus_id()")
>>
>> in the char-misc tree.
>
> That's because the nvmem maintainer sent these to me for inclusion, odd.
Am happy to send a PR next time if it helps.
thanks,
srini
>
> greg k-h
next prev parent reply other threads:[~2023-12-18 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 5:12 linux-next: duplicate patches in the nvmem tree Stephen Rothwell
2023-12-18 10:26 ` Greg KH
2023-12-18 10:38 ` Srinivas Kandagatla [this message]
2023-12-18 10:30 ` Srinivas Kandagatla
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 5:42 Stephen Rothwell
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=681bfda0-ccc2-4af0-b77e-31c92cf7ada3@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).