mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: Mark Brown <broonie@kernel.org>, Srinivas Kandagatla <srini@kernel.org>
Cc: 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: Fri, 31 Jul 2026 16:59:51 +0100	[thread overview]
Message-ID: <42c97254-957b-4144-92ab-7edec194384d@oss.qualcomm.com> (raw)
In-Reply-To: <amy62FeftQnnQ350@sirena.org.uk>



On 7/31/26 4:10 PM, Mark Brown wrote:
> Hi all,
> 
> The following commit is also in the char-misc tree as a different commit
> (but the same patch):
> 

I will drop these patches Mark, normally all the nvmem patches go via
Greg's char-misc tree, so there is a overlap for few days while Greg
applies this to char-misc tree.

--srini

>   18f2b79951a9e ("nvmem: qcom: Unify user-visible "Qualcomm" name")
>   512946cf0f32e ("nvmem: rockchip-otp: alloc clks with main struct")
>   5a2bba5b74227 ("dt-bindings: nvmem: lan9662-otpc: Add LAN969x series")
>   68628e84bc61e ("dt-bindings: nvmem: airoha: add SMC eFuses schema")
>   7089170e1df16 ("nvmem: apple-spmi-nvmem: wrap regmap calls to satisfy CFI")
>   7106dcb57aa1b ("nvmem: core: Default to read-only if wp-gpios present")
>   7592c50152619 ("nvmem: lan9662-otp: add support for LAN969x")
>   9f902e68cfe33 ("dt-bindings: nvmem: qfprom: Add Milos compatible")
>   a3122a19f00b7 ("nvmem: layouts: u-boot-env: check earlier for ethaddr length")
>   ac0a5d17aa3cc ("dt-bindings: nvmem: qcom,qfprom: Add Shikra compatible")
>   b13e7886c2e16 ("nvmem: airoha: Add support for SMC eFUSE")
>   c00ca6cc2fc96 ("nvmem: layouts: Add fixed-layout driver")
>   c33862c0a3a9a ("dt-bindings: nvmem: qfprom: Add glymur compatible")
>   c896d1c34f2bb ("dt-bindings: nvmem: qfprom: qcom: Add Hawi compatible")
>   d5bd22d9d2032 ("nvmem: cleanup dead code in Kconfig")


  reply	other threads:[~2026-07-31 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 15:10 Mark Brown
2026-07-31 15:59 ` Srinivas Kandagatla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-20 14:55 Mark Brown
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-12-10 21:48 Stephen Rothwell
2023-12-11 10:34 ` Miquel Raynal
2023-12-11 11:09   ` Srinivas Kandagatla
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=42c97254-957b-4144-92ab-7edec194384d@oss.qualcomm.com \
    --to=srinivas.kandagatla@oss.qualcomm.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=srini@kernel.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

all inboxes | Powered by JetHome®