From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Li Yang <leoyang.li@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] arm64: dts: ls1028a: add efuse node
Date: Mon, 21 Feb 2022 11:51:34 +0800 [thread overview]
Message-ID: <20220221035134.GH2249@dragon> (raw)
In-Reply-To: <20220214115529.662948-4-michael@walle.cc>
On Mon, Feb 14, 2022 at 12:55:29PM +0100, Michael Walle wrote:
> Layerscape SoCs contain a Security Fuse Processor which is basically a
> efuse controller. Add the node, so userspace can read the efuses.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-21 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 11:55 [PATCH v2 0/3] nvmem: add Layerscape SFP support Michael Walle
2022-02-14 11:55 ` [PATCH v2 1/3] dt-bindings: nvmem: add fsl,layerscape-sfp binding Michael Walle
2022-02-14 11:55 ` [PATCH v2 2/3] nvmem: add driver for Layerscape SFP (Security Fuse Processor) Michael Walle
2022-02-14 11:55 ` [PATCH v2 3/3] arm64: dts: ls1028a: add efuse node Michael Walle
2022-02-21 3:51 ` Shawn Guo [this message]
2022-02-14 11:58 ` [PATCH v2 0/3] nvmem: add Layerscape SFP support 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=20220221035134.GH2249@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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 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).