From: Rob Herring <robh@kernel.org>
To: Sven Peter <sven@svenpeter.dev>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowsk <krzysztof.kozlowski@canonical.com>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Mark Kettenis <kettenis@openbsd.org>,
linux-arm-kernel@lists.infradead.org,
Hector Martin <marcan@marcan.st>,
Rob Herring <robh+dt@kernel.org>, Joey Gouly <joey.gouly@arm.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: nvmem: Add apple,efuses
Date: Sun, 20 Mar 2022 14:20:08 -0400 [thread overview]
Message-ID: <YjdwWHQNg8Ro+DIr@robh.at.kernel.org> (raw)
In-Reply-To: <20220312165837.40687-1-sven@svenpeter.dev>
On Sat, 12 Mar 2022 17:58:36 +0100, Sven Peter wrote:
> Apple SoCs come with eFuses used to store factory-programmed data
> such as calibration settings for the PCIe and Type-C PHY.
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> Signed-off-by: Sven Peter <sven@svenpeter.dev>
> ---
> v2 -> v3:
> - added r-b tag
> v1 -> v2:
> - fixed indentation issue pointed out by Krzysztof Kozlowski
>
> .../bindings/nvmem/apple,efuses.yaml | 50 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/apple,efuses.yaml
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-03-20 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 16:58 [PATCH v3 1/2] dt-bindings: nvmem: Add apple,efuses Sven Peter
2022-03-12 16:58 ` [PATCH v3 2/2] nvmem: Add Apple eFuse driver Sven Peter
2022-04-08 10:18 ` Srinivas Kandagatla
2022-03-20 18:20 ` Rob Herring [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=YjdwWHQNg8Ro+DIr@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alyssa@rosenzweig.io \
--cc=devicetree@vger.kernel.org \
--cc=joey.gouly@arm.com \
--cc=kettenis@openbsd.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=sven@svenpeter.dev \
/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).