From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Cc: "Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Michael Walle" <michael@walle.cc>,
gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, u-boot@lists.denx.de,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V2 0/3] nvmem: support post read for U-Boot's "ethaddr"
Date: Thu, 23 Mar 2023 08:23:40 +0000 [thread overview]
Message-ID: <7e9ee8e2-988e-1f51-e7ed-19f9e3181d9e@linaro.org> (raw)
In-Reply-To: <20230318171356.29515-1-zajec5@gmail.com>
On 18/03/2023 17:13, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> This change is required for NVMEM consumers to get expected MAC address
> from U-Boot env data variable "ethaddr".
>
> To address some previous concerns:
> 1. Yes, U-Boot env binding & driver should be converted to NVMEM layout
> 2. My priority is to get working MAC rather than fancy DT syntax
> 3. I AM going to convert U-Boot env into layout later
> 4. This work DOESN'T conflict with layout migration
> 5. This code WILL stay during / after layout migration
>
> My brain limitations don't allow me to handle everything at once, please
> let's review what I already have here.
Thanks for your patience.
Applied now,
--srini
>
> Rafał Miłecki (3):
> dt-bindings: nvmem: u-boot,env: add MAC's #nvmem-cell-cells
> nvmem: core: support specifying both: cell raw data & post read
> lengths
> nvmem: u-boot-env: post-process "ethaddr" env variable
>
> .../devicetree/bindings/nvmem/u-boot,env.yaml | 7 ++++-
> drivers/nvmem/Kconfig | 1 +
> drivers/nvmem/core.c | 11 +++++---
> drivers/nvmem/u-boot-env.c | 26 +++++++++++++++++++
> include/linux/nvmem-provider.h | 2 ++
> 5 files changed, 42 insertions(+), 5 deletions(-)
>
prev parent reply other threads:[~2023-03-23 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 17:13 [PATCH V2 0/3] nvmem: support post read for U-Boot's "ethaddr" Rafał Miłecki
2023-03-18 17:13 ` [PATCH V2 1/3] dt-bindings: nvmem: u-boot,env: add MAC's #nvmem-cell-cells Rafał Miłecki
2023-03-18 17:13 ` [PATCH V2 2/3] nvmem: core: support specifying both: cell raw data & post read lengths Rafał Miłecki
2023-03-18 17:13 ` [PATCH V2 3/3] nvmem: u-boot-env: post-process "ethaddr" env variable Rafał Miłecki
2023-03-23 8:23 ` 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=7e9ee8e2-988e-1f51-e7ed-19f9e3181d9e@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=u-boot@lists.denx.de \
--cc=zajec5@gmail.com \
/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 NNTP newsgroup(s).