From: Lee Jones <lee@kernel.org>
To: srini@kernel.org, Heiko Stuebner <heiko@sntech.de>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 1/2] dt-bindings: mfd: qnap,ts433-mcu: allow nvmem-layout child node
Date: Thu, 31 Jul 2025 14:48:13 +0100 [thread overview]
Message-ID: <20250731134813.GJ1049189@google.com> (raw)
In-Reply-To: <175396964012.1212829.4001330716835123166.b4-ty@kernel.org>
On Thu, 31 Jul 2025, Lee Jones wrote:
> On Wed, 30 Jul 2025 19:22:47 +0200, Heiko Stuebner wrote:
> > The MCU has an eeprom memory connected internally, that for example
> > contains some mac-addresses for the soc gmac controllers.
> >
> > Therefore allow defining the nvmem-layout for the eeprom.
> >
> >
>
> Applied, thanks!
>
> [1/2] dt-bindings: mfd: qnap,ts433-mcu: allow nvmem-layout child node
> commit: 17edd13a0916c7c84966b4db96fe744986c3a04b
This should have been applied to the previous set.
I eventually worked out why it wasn't applying cleanly.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-07-31 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 17:22 [PATCH 0/2] qnap-mcu: add nvmem subdevice to read the eeprom Heiko Stuebner
2025-07-30 17:22 ` [PATCH 1/2] dt-bindings: mfd: qnap,ts433-mcu: allow nvmem-layout child node Heiko Stuebner
2025-07-31 0:18 ` Rob Herring (Arm)
2025-07-31 13:47 ` (subset) " Lee Jones
2025-07-31 13:48 ` Lee Jones [this message]
2025-07-30 17:22 ` [PATCH 2/2] nvmem: add driver for the eeprom in qnap-mcu controllers Heiko Stuebner
2025-09-09 5:51 ` Srinivas Kandagatla
2025-09-11 8:41 ` Lee Jones
2025-09-11 8:48 ` Heiko Stübner
2025-09-11 14:44 ` Lee Jones
2025-08-18 6:41 ` (subset) [PATCH 0/2] qnap-mcu: add nvmem subdevice to read the eeprom Srinivas Kandagatla
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=20250731134813.GJ1049189@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 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.