From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the nvmem tree
Date: Mon, 6 Feb 2023 08:32:15 +1100 [thread overview]
Message-ID: <20230206083215.723e7f72@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
03b6f71ceeb1 ("nvmem: core: fix cleanup after dev_set_name()")
6b868c1a2ec0 ("nvmem: sunxi_sid: Always use 32-bit MMIO reads")
957b1f840ce0 ("nvmem: brcm_nvram: Add check for kzalloc")
9afef75ce71c ("nvmem: core: remove nvmem_config wp_gpio")
a895af2746e3 ("nvmem: core: fix return value")
b02c75889942 ("nvmem: core: fix registration vs use race")
b3a9be9040b7 ("nvmem: core: initialise nvmem->id early")
ba716d020bc8 ("nvmem: qcom-spmi-sdam: fix module autoloading")
c976fd0b6970 ("nvmem: core: fix device node refcounting")
ee29286033ef ("nvmem: core: fix cell removal on error")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-05 21:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 21:32 Stephen Rothwell [this message]
2023-03-05 23:51 ` linux-next: duplicate patches in the nvmem tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2023-05-08 1:00 Stephen Rothwell
2023-07-03 21:58 Stephen Rothwell
2023-09-04 22:04 Stephen Rothwell
2023-09-25 22:34 Stephen Rothwell
2023-09-26 6:03 ` Srinivas Kandagatla
2023-10-17 4:07 Stephen Rothwell
2023-10-17 5:45 ` Srinivas Kandagatla
2023-10-25 4:23 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
2024-05-06 5:42 Stephen Rothwell
2024-09-04 6:06 Stephen Rothwell
2024-11-05 5:59 Stephen Rothwell
2024-11-05 9:46 ` Greg KH
2024-11-05 11:21 ` Srinivas Kandagatla
2025-05-23 6:35 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=20230206083215.723e7f72@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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