From: Rob Herring <robh@kernel.org>
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: linux-kernel@vger.kernel.org, Drazen Spio <drazsp@gmail.com>,
linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: amlogic: add MeCool KII/KIII Pro bindings
Date: Tue, 30 Mar 2021 17:20:44 -0500 [thread overview]
Message-ID: <20210330222044.GA817353@robh.at.kernel.org> (raw)
In-Reply-To: <20210329154753.30074-2-christianshewitt@gmail.com>
On Mon, 29 Mar 2021 15:47:51 +0000, Christian Hewitt wrote:
> Add the board bindings for the MeCool (Videostrong Technology Co., Ltd)
> KII-Pro (S905D) and KIII-Pro (S912) devices.
>
> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/amlogic.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2021-03-30 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 15:47 [PATCH 0/3] arm64: dts: meson: add support for MeCool KII-Pro/KIII-Pro Christian Hewitt
2021-03-29 15:47 ` [PATCH 1/3] dt-bindings: arm: amlogic: add MeCool KII/KIII Pro bindings Christian Hewitt
2021-03-30 22:20 ` Rob Herring [this message]
2021-03-29 15:47 ` [PATCH 2/3] arm64: dts: meson: add initial device-tree for MeCool KII Pro Christian Hewitt
2021-03-30 15:25 ` Neil Armstrong
2021-03-29 15:47 ` [PATCH 3/3] arm64: dts: meson: add initial device-tree for MeCool KIII Pro Christian Hewitt
2021-03-30 15:25 ` Neil Armstrong
2021-03-31 21:43 ` [PATCH 0/3] arm64: dts: meson: add support for MeCool KII-Pro/KIII-Pro Kevin Hilman
2021-04-07 16:17 ` Kevin Hilman
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=20210330222044.GA817353@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=drazsp@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).