From: Rob Herring <robh@kernel.org>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Cc: linux-kernel@vger.kernel.org, hsinyi@chromium.org,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org,
Ryder Lee <ryder.lee@kernel.org>,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: [PATCH v10 2/4] dt-bindings: arm: mediatek: Add mt8186 pericfg compatible
Date: Tue, 10 May 2022 12:21:01 -0500 [thread overview]
Message-ID: <Ynqe/d2+UT1V8Y+3@robh.at.kernel.org> (raw)
In-Reply-To: <20220510075233.5426-3-allen-kh.cheng@mediatek.com>
On Tue, 10 May 2022 15:52:31 +0800, Allen-KH Cheng wrote:
> Add mt8186 pericfg compatible to binding document.
>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> ---
> .../devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-05-10 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 7:52 [PATCH v10 0/4] Add basic node support for MediaTek MT8186 SoC Allen-KH Cheng
2022-05-10 7:52 ` [PATCH v10 1/4] dt-bindings: timer: Add compatible for Mediatek MT8186 Allen-KH Cheng
2022-05-11 14:12 ` Rob Herring
2022-05-10 7:52 ` [PATCH v10 2/4] dt-bindings: arm: mediatek: Add mt8186 pericfg compatible Allen-KH Cheng
2022-05-10 17:21 ` Rob Herring [this message]
2022-05-10 7:52 ` [PATCH v10 3/4] dt-bindings: arm: Add compatible for MediaTek MT8186 Allen-KH Cheng
2022-05-10 17:21 ` 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=Ynqe/d2+UT1V8Y+3@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@chromium.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@kernel.org \
--cc=wenst@chromium.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).