From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Andrew-CT Chen" <andrew-ct.chen@mediatek.com>,
"Lala Lin" <lala.lin@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V2 1/2] dt-bindings: nvmem: mediatek: efuse: add support for MT7981
Date: Tue, 11 Jun 2024 07:44:57 -0600 [thread overview]
Message-ID: <20240611134457.GA1796783-robh@kernel.org> (raw)
In-Reply-To: <20240514015154.11206-1-zajec5@gmail.com>
On Tue, May 14, 2024 at 03:51:53AM +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Add compatible for MT7981 SoC.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> V2: Use new compatible instead of MT7986's one
>
> Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml | 1 +
> 1 file changed, 1 insertion(+)
Looks like this was missed, so I've applied it.
Rob
prev parent reply other threads:[~2024-06-11 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 1:51 [PATCH V2 1/2] dt-bindings: nvmem: mediatek: efuse: add support for MT7981 Rafał Miłecki
2024-05-14 1:51 ` [PATCH V2 2/2] arm64: dts: mediatek: mt7981: add efuse block Rafał Miłecki
2024-05-14 12:15 ` AngeloGioacchino Del Regno
2024-05-14 7:32 ` [PATCH V2 1/2] dt-bindings: nvmem: mediatek: efuse: add support for MT7981 Krzysztof Kozlowski
2024-05-14 12:15 ` AngeloGioacchino Del Regno
2024-06-03 7:38 ` (subset) " AngeloGioacchino Del Regno
2024-06-11 9:30 ` Srinivas Kandagatla
2024-06-11 13:44 ` 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=20240611134457.GA1796783-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lala.lin@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=rafal@milecki.pl \
--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).