From: patchwork-bot+linux-amlogic@kernel.org
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH v4 0/5] arm64: dts: meson: add W400 dtsi and GT-King/Pro devices
Date: Wed, 20 May 2020 23:01:11 +0000 [thread overview]
Message-ID: <159001567153.22936.9218155925699663707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200520014329.12469-1-christianshewitt@gmail.com>
Hello:
This series was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Wed, 20 May 2020 01:43:24 +0000 you wrote:
> This series combines patch 2 from [1] which converts the existing Ugoos
> AM6 device-tree to a common W400 dtsi and dts, and then reworks the
> Beelink GT-King/GT-King Pro series from [2] to use the dtsi, but this
> time without the offending common audio dtsi approach. I've carried
> forwards acks on bindings from Rob as these did not change.
>
> v4 - rebased against Kevin's v5.8/dt64 branch
>
> [...]
Here is a summary with links:
- [v4,1/5] arm64: dts: meson: convert ugoos-am6 to common w400 dtsi
https://git.kernel.org/khilman/linux-amlogic/c/3cb74db9b2561a25701b9024b9d5c0077c43e214
- [v4,2/5] dt-bindings: arm: amlogic: add support for the Beelink GT-King
https://git.kernel.org/khilman/linux-amlogic/c/3a90ef281f852db9900024116e8ea93a49115df9
- [v4,3/5] arm64: dts: meson-g12b-gtking: add initial device-tree
https://git.kernel.org/khilman/linux-amlogic/c/c5522ff9c7299f9845df3fd521d51a1ef7617ac7
- [v4,4/5] dt-bindings: arm: amlogic: add support for the Beelink GT-King Pro
https://git.kernel.org/khilman/linux-amlogic/c/8d4b8772296f88e0b6bf5d091ebf25a54e51882c
- [v4,5/5] arm64: dts: meson-g12b-gtking-pro: add initial device-tree
https://git.kernel.org/khilman/linux-amlogic/c/0b928e4e412b1eb9e79e02cf3580b9254d338aae
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-05-20 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 1:43 [PATCH v4 0/5] arm64: dts: meson: add W400 dtsi and GT-King/Pro devices Christian Hewitt
2020-05-20 1:43 ` [PATCH v4 1/5] arm64: dts: meson: convert ugoos-am6 to common w400 dtsi Christian Hewitt
2020-05-20 1:43 ` [PATCH v4 2/5] dt-bindings: arm: amlogic: add support for the Beelink GT-King Christian Hewitt
2020-05-20 1:43 ` [PATCH v4 3/5] arm64: dts: meson-g12b-gtking: add initial device-tree Christian Hewitt
2020-05-20 1:43 ` [PATCH v4 4/5] dt-bindings: arm: amlogic: add support for the Beelink GT-King Pro Christian Hewitt
2020-05-20 1:43 ` [PATCH v4 5/5] arm64: dts: meson-g12b-gtking-pro: add initial device-tree Christian Hewitt
2020-05-20 22:57 ` [PATCH v4 0/5] arm64: dts: meson: add W400 dtsi and GT-King/Pro devices Kevin Hilman
2020-05-20 23:01 ` patchwork-bot+linux-amlogic [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=159001567153.22936.9218155925699663707.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=christianshewitt@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.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).