From: Srinivas Kandagatla <srini@kernel.org>
To: Rob Herring <robh@kernel.org>, srini@kernel.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/14] nvmem: patches for 7.2
Date: Mon, 29 Jun 2026 21:10:01 +0100 [thread overview]
Message-ID: <2dfe016d-5ee7-4d46-846e-3b276e1f4024@kernel.org> (raw)
In-Reply-To: <20260629175334.GA2835144-robh@kernel.org>
On 6/29/26 6:53 PM, Rob Herring wrote:
> On Sat, May 30, 2026 at 09:53:19PM +0100, srini@kernel.org wrote:
>> From: Srinivas Kandagatla <srini@kernel.org>
>>
>> Hi Greg,
>>
>> Here are few nvmem patches for 7.2, Could you please queue
>> these for 7.2.
>>
>> Patches include
>> - Device tree bindings for Milos, airoha, lan9662, Shikra,
>> Hawi, glymur providers.
>> - some code cleanup in Kconfig, rockchip, nintendo providers.
>> - clarify default read-only behaviour for wp-gpios
>> - airoha new nvmem provider driver
>>
>> Thanks,
>> Srini
>
> Some reason this didn't go into 7.2? The .dts side did and now we have
> warnings because the bindings are missing.
Yes, looks like it got missed for some reason.
Greg, these patches cleanly apply on 7.2-rc1 too, could you please pick
these up.
thanks,
Srini
>
> Rob
prev parent reply other threads:[~2026-06-29 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 20:53 [PATCH 00/14] nvmem: patches for 7.2 srini
2026-05-30 20:53 ` [PATCH 01/14] dt-bindings: nvmem: qfprom: Add glymur compatible srini
2026-05-30 20:53 ` [PATCH 02/14] nvmem: rockchip-otp: alloc clks with main struct srini
2026-05-30 20:53 ` [PATCH 03/14] nvmem: core: Default to read-only if wp-gpios present srini
2026-05-30 20:53 ` [PATCH 04/14] dt-bindings: nvmem: qfprom: qcom: Add Hawi compatible srini
2026-05-30 20:53 ` [PATCH 05/14] nvmem: nintendo-otp: Use of_device_get_match_data() srini
2026-05-30 20:53 ` [PATCH 06/14] dt-bindings: nvmem: qfprom: Add Milos compatible srini
2026-05-30 20:53 ` [PATCH 07/14] dt-bindings: nvmem: lan9662-otpc: Add LAN969x series srini
2026-05-30 20:53 ` [PATCH 08/14] nvmem: lan9662-otp: add support for LAN969x srini
2026-05-30 20:53 ` [PATCH 09/14] dt-bindings: nvmem: qcom,qfprom: Add Shikra compatible srini
2026-05-30 20:53 ` [PATCH 10/14] dt-bindings: nvmem: airoha: add SMC eFuses schema srini
2026-05-30 20:53 ` [PATCH 11/14] nvmem: airoha: Add support for SMC eFUSE srini
2026-05-30 20:53 ` [PATCH 12/14] nvmem: qcom: Unify user-visible "Qualcomm" name srini
2026-05-30 20:53 ` [PATCH 13/14] nvmem: cleanup dead code in Kconfig srini
2026-05-30 20:53 ` [PATCH 14/14] nvmem: layouts: u-boot-env: check earlier for ethaddr length srini
2026-06-29 17:53 ` [PATCH 00/14] nvmem: patches for 7.2 Rob Herring
2026-06-29 20:10 ` Srinivas Kandagatla [this message]
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=2dfe016d-5ee7-4d46-846e-3b276e1f4024@kernel.org \
--to=srini@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.