From: Kevin Hilman <khilman@baylibre.com>
To: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
Christian Hewitt <christianshewitt@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] arm64: dts: meson: add support for WeTek Core 2
Date: Tue, 21 Jul 2020 14:14:45 -0700 [thread overview]
Message-ID: <159536607960.30777.1598266947126340920.b4-ty@baylibre.com> (raw)
In-Reply-To: <20200719021421.7959-1-christianshewitt@gmail.com>
On Sun, 19 Jul 2020 02:14:19 +0000, Christian Hewitt wrote:
> This series adds support for the WeTek Core 2 which is a commercial box
> device based on the Amlogic Q200 reference design.
>
> v3 changes - fix BT node (enable-gpios > shutdown-gpios)
> v2 changes - simplify ethernet disable
>
> Christian Hewitt (2):
> dt-bindings: arm: amlogic: add support for the WeTek Core 2
> arm64: dts: meson: add support for the WeTek Core 2
>
> [...]
Applied, thanks!
[1/2] dt-bindings: arm: amlogic: add support for the WeTek Core 2
commit: 8b6f53d7b94b8d23860ae44a56b0af404a6c7e4c
[2/2] arm64: dts: meson: add support for the WeTek Core 2
commit: ea232b9ccccf2f55fe231441f3908c31c7136c4f
Best regards,
--
Kevin Hilman <khilman@baylibre.com>
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
Christian Hewitt <christianshewitt@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] arm64: dts: meson: add support for WeTek Core 2
Date: Tue, 21 Jul 2020 14:14:45 -0700 [thread overview]
Message-ID: <159536607960.30777.1598266947126340920.b4-ty@baylibre.com> (raw)
In-Reply-To: <20200719021421.7959-1-christianshewitt@gmail.com>
On Sun, 19 Jul 2020 02:14:19 +0000, Christian Hewitt wrote:
> This series adds support for the WeTek Core 2 which is a commercial box
> device based on the Amlogic Q200 reference design.
>
> v3 changes - fix BT node (enable-gpios > shutdown-gpios)
> v2 changes - simplify ethernet disable
>
> Christian Hewitt (2):
> dt-bindings: arm: amlogic: add support for the WeTek Core 2
> arm64: dts: meson: add support for the WeTek Core 2
>
> [...]
Applied, thanks!
[1/2] dt-bindings: arm: amlogic: add support for the WeTek Core 2
commit: 8b6f53d7b94b8d23860ae44a56b0af404a6c7e4c
[2/2] arm64: dts: meson: add support for the WeTek Core 2
commit: ea232b9ccccf2f55fe231441f3908c31c7136c4f
Best regards,
--
Kevin Hilman <khilman@baylibre.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
Christian Hewitt <christianshewitt@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] arm64: dts: meson: add support for WeTek Core 2
Date: Tue, 21 Jul 2020 14:14:45 -0700 [thread overview]
Message-ID: <159536607960.30777.1598266947126340920.b4-ty@baylibre.com> (raw)
In-Reply-To: <20200719021421.7959-1-christianshewitt@gmail.com>
On Sun, 19 Jul 2020 02:14:19 +0000, Christian Hewitt wrote:
> This series adds support for the WeTek Core 2 which is a commercial box
> device based on the Amlogic Q200 reference design.
>
> v3 changes - fix BT node (enable-gpios > shutdown-gpios)
> v2 changes - simplify ethernet disable
>
> Christian Hewitt (2):
> dt-bindings: arm: amlogic: add support for the WeTek Core 2
> arm64: dts: meson: add support for the WeTek Core 2
>
> [...]
Applied, thanks!
[1/2] dt-bindings: arm: amlogic: add support for the WeTek Core 2
commit: 8b6f53d7b94b8d23860ae44a56b0af404a6c7e4c
[2/2] arm64: dts: meson: add support for the WeTek Core 2
commit: ea232b9ccccf2f55fe231441f3908c31c7136c4f
Best regards,
--
Kevin Hilman <khilman@baylibre.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-07-21 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 2:14 [PATCH v3 0/2] arm64: dts: meson: add support for WeTek Core 2 Christian Hewitt
2020-07-19 2:14 ` Christian Hewitt
2020-07-19 2:14 ` Christian Hewitt
2020-07-19 2:14 ` [PATCH v3 1/2] dt-bindings: arm: amlogic: add support for the " Christian Hewitt
2020-07-19 2:14 ` Christian Hewitt
2020-07-19 2:14 ` Christian Hewitt
2020-07-19 2:14 ` [PATCH v3 2/2] arm64: dts: meson: " Christian Hewitt
2020-07-19 2:14 ` Christian Hewitt
2020-07-19 2:14 ` Christian Hewitt
2020-07-21 8:05 ` Neil Armstrong
2020-07-21 8:05 ` Neil Armstrong
2020-07-21 8:05 ` Neil Armstrong
2020-07-21 21:14 ` Kevin Hilman [this message]
2020-07-21 21:14 ` [PATCH v3 0/2] arm64: dts: meson: add support for " Kevin Hilman
2020-07-21 21:14 ` Kevin Hilman
2020-07-21 21:21 ` patchwork-bot+linux-amlogic
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=159536607960.30777.1598266947126340920.b4-ty@baylibre.com \
--to=khilman@baylibre.com \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.