From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Michael Walle" <michael@walle.cc>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
linux-mtd@lists.infradead.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 V3 6/6] nvmem: layouts: add U-Boot env layout
Date: Thu, 4 Jan 2024 16:46:14 +0100 [thread overview]
Message-ID: <2024010446-willfully-swoop-8510@gregkh> (raw)
In-Reply-To: <20231221173421.13737-6-zajec5@gmail.com>
On Thu, Dec 21, 2023 at 06:34:21PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Move all generic (NVMEM devices independent) code from NVMEM device
> driver to NVMEM layout driver. Then add a simple NVMEM layout code on
> top of it.
>
> Thanks to proper layout it's possible to support U-Boot env data stored
> on any kind of NVMEM device.
>
> For backward compatibility with old DT bindings we need to keep old
> NVMEM device driver functional. To avoid code duplication export and
> reuse a parsing function.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> V2: Support new compatibles & use device_get_match_data() helper
> V3: Use imperative in commit body
>
> IMPORTANT:
> This is based on top of the:
> [PATCH v6.8 1/2] nvmem: layouts: refactor .add_cells() callback arguments
I applied patches 2-5 in this series, I'll let you rebase the remaining
two after addressing the issues discussed in patch 1.
thanks,
gre gk-h
next prev parent reply other threads:[~2024-01-04 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 17:34 [PATCH V3 1/6] dt-bindings: nvmem: layouts: add U-Boot environment variables layout Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 2/6] nvmem: core: add nvmem_dev_size() helper Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 3/6] nvmem: u-boot-env: use nvmem_add_one_cell() nvmem subsystem helper Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 4/6] nvmem: u-boot-env: use nvmem device helpers Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 5/6] nvmem: u-boot-env: improve coding style Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 6/6] nvmem: layouts: add U-Boot env layout Rafał Miłecki
2024-01-04 15:46 ` Greg Kroah-Hartman [this message]
2024-01-04 0:11 ` [PATCH V3 1/6] dt-bindings: nvmem: layouts: add U-Boot environment variables layout Rob Herring
2024-01-04 7:58 ` Miquel Raynal
2024-01-04 9:10 ` Rafał Miłecki
2024-01-15 17:09 ` Rob Herring
2024-01-15 22:10 ` Miquel Raynal
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=2024010446-willfully-swoop-8510@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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).