From: Tom Rini <trini@konsulko.com>
To: "Marek Behún" <kabel@kernel.org>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Luka Kovacic <luka.kovacic@sartura.hr>
Subject: Re: [PATCH RFC linux] dt-bindings: nvmem: Add binding for U-Boot environment NVMEM provider
Date: Thu, 14 Oct 2021 09:33:43 -0400 [thread overview]
Message-ID: <20211014133343.GA7964@bill-the-cat> (raw)
In-Reply-To: <20211013232048.16559-1-kabel@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On Thu, Oct 14, 2021 at 01:20:48AM +0200, Marek Behún wrote:
> Add device tree bindings for U-Boot environment NVMEM provider.
>
> U-Boot environment can be stored at a specific offset of a MTD device,
> EEPROM, MMC, NAND or SATA device, on an UBI volume, or in a file on a
> filesystem.
>
> The environment can contain information such as device's MAC address,
> which should be used by the ethernet controller node.
>
> Signed-off-by: Marek Behún <kabel@kernel.org>
> ---
> .../bindings/nvmem/denx,u-boot-env.yaml | 88 +++++++++++++++++++
We already have a vendor prefix for U-Boot, "u-boot" which should be
used here.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-10-14 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 23:20 [PATCH RFC linux] dt-bindings: nvmem: Add binding for U-Boot environment NVMEM provider Marek Behún
2021-10-14 8:26 ` Srinivas Kandagatla
2021-10-14 10:06 ` Marek Behún
2021-10-14 10:30 ` Srinivas Kandagatla
2021-10-14 10:55 ` Marek Behún
2021-10-14 11:36 ` Srinivas Kandagatla
2021-10-14 13:33 ` Tom Rini [this message]
2021-10-14 14:31 ` Rob Herring
2021-10-14 14:41 ` Rob Herring
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=20211014133343.GA7964@bill-the-cat \
--to=trini@konsulko.com \
--cc=devicetree@vger.kernel.org \
--cc=kabel@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.kovacic@sartura.hr \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=u-boot@lists.denx.de \
/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.