From: Matthias Brugger <matthias.bgg@gmail.com>
To: Fabien Parent <fparent@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Sean Wang <sean.wang@mediatek.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/3] dt-bindings: arm64: dts: mediatek: Add mt8167-pumpkin board
Date: Fri, 27 Nov 2020 09:38:21 +0100 [thread overview]
Message-ID: <75a1835b-14a1-f86d-bae6-6377e50e1864@gmail.com> (raw)
In-Reply-To: <20201027194816.1227654-1-fparent@baylibre.com>
On 27/10/2020 20:48, Fabien Parent wrote:
> Add binding documentation for the MT8167 Pumpkin board.
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> ---
> Documentation/devicetree/bindings/arm/mediatek.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
All three patches applied to v5.10-next/dts64
Thanks!
> diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
> index 30908963ae26..5c772b937efc 100644
> --- a/Documentation/devicetree/bindings/arm/mediatek.yaml
> +++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
> @@ -84,6 +84,10 @@ properties:
> - enum:
> - mediatek,mt8135-evbp1
> - const: mediatek,mt8135
> + - items:
> + - enum:
> + - mediatek,mt8167-pumpkin
> + - const: mediatek,mt8167
> - description: Google Elm (Acer Chromebook R13)
> items:
> - const: google,elm-rev8
>
prev parent reply other threads:[~2020-11-27 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 19:48 [PATCH 1/3] dt-bindings: arm64: dts: mediatek: Add mt8167-pumpkin board Fabien Parent
2020-10-27 19:48 ` [PATCH 2/3] arm64: dts: mediatek: add dtsi for MT8167 Fabien Parent
2020-10-27 19:48 ` [PATCH 3/3] arm64: dts: mediatek: add MT8167 pumpkin board dts Fabien Parent
2020-10-30 19:17 ` [PATCH 1/3] dt-bindings: arm64: dts: mediatek: Add mt8167-pumpkin board Rob Herring
2020-11-27 8:38 ` Matthias Brugger [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=75a1835b-14a1-f86d-bae6-6377e50e1864@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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).