From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Rafał Miłecki" <rafal@milecki.pl>,
linux-arm-kernel@lists.infradead.org,
"Vivek Unune" <npcomplete13@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
"Rob Herring" <robh+dt@kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V2 1/2] dt-bindings: nvmem: add Broadcom's NVRAM
Date: Tue, 9 Mar 2021 20:02:22 -0700 [thread overview]
Message-ID: <20210310030222.GA1667188@robh.at.kernel.org> (raw)
In-Reply-To: <20210305183236.11784-1-zajec5@gmail.com>
On Fri, 05 Mar 2021 19:32:35 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Broadcom's NVRAM structure contains device data and can be accessed
> using I/O mapping.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> V2: Use Broadcom's NVRAM specific binding. Generic "nvmem-iomap" binding
> didn't make much sense. Thanks Srinivas!
> ---
> .../devicetree/bindings/nvmem/brcm,nvram.yaml | 34 +++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-03-10 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 18:32 [PATCH V2 1/2] dt-bindings: nvmem: add Broadcom's NVRAM Rafał Miłecki
2021-03-05 18:32 ` [PATCH V2 2/2] nvmem: brcm_nvram: new driver exposing " Rafał Miłecki
2021-03-10 3:02 ` Rob Herring [this message]
2021-03-10 10:23 ` [PATCH V2 1/2] dt-bindings: nvmem: add " 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=20210310030222.GA1667188@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=npcomplete13@gmail.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--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).