From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
narmstrong@baylibre.com, catalin.marinas@arm.com,
will.deacon@arm.com, robh+dt@kernel.org, carlo@caione.org,
linux-amlogic@lists.infradead.org, gouwa@szwesion.com,
afaerber@suse.de, linux-arm-kernel@lists.infradead.org,
jbrunet@baylibre.com
Subject: Re: [PATCH 0/3] Khadas VIM support (Amlogic Meson GXL S905X)
Date: Wed, 22 Mar 2017 09:17:27 -0700 [thread overview]
Message-ID: <m2zigdmgko.fsf@baylibre.com> (raw)
In-Reply-To: <20170304215126.7020-1-martin.blumenstingl@googlemail.com> (Martin Blumenstingl's message of "Sat, 4 Mar 2017 22:51:23 +0100")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> This series adds support for the Khadas VIM and Khadas VIM Pro boards
> (both are provided through a single .dts as the only two differences are
> the eMMC size and different SDIO WIFI chips - both are Broadcom brcmfmac
> based though).
> More details can be found on the official website: [0]
>
> I have tested this on a Khadas VIM Pro board. It would be nice if someone
> with a non-Pro board could give it a try as well.
Applied to v4.12/dt64
After all the discussion, I left patch 1 as is.
Kevin
prev parent reply other threads:[~2017-03-22 16:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 21:51 [PATCH 0/3] Khadas VIM support (Amlogic Meson GXL S905X) Martin Blumenstingl
[not found] ` <20170304215126.7020-1-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-03-04 21:51 ` [PATCH 1/3] devicetree: add vendor prefix for Khadas Martin Blumenstingl
[not found] ` <20170304215126.7020-2-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-03-15 19:57 ` Rob Herring
2017-03-16 6:00 ` Andreas Färber
[not found] ` <61778a7a-3d96-8de3-fd4f-f18aa0938a68-l3A5Bk7waGM@public.gmane.org>
2017-03-16 21:14 ` Martin Blumenstingl
2017-03-17 3:13 ` Gouwa
2017-03-04 21:51 ` [PATCH 2/3] dt-bindings: amlogic: add the Khadas VIM Martin Blumenstingl
[not found] ` <20170304215126.7020-3-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-03-15 19:58 ` Rob Herring
2017-03-04 21:51 ` [PATCH 3/3] ARM64: dts: meson-gxl: add support for the Khadas VIM board Martin Blumenstingl
2017-03-06 16:12 ` [PATCH 0/3] Khadas VIM support (Amlogic Meson GXL S905X) Neil Armstrong
2017-03-18 12:36 ` [PATCH v2 " Martin Blumenstingl
2017-03-18 12:36 ` [PATCH v2 2/3] dt-bindings: amlogic: add the Khadas VIM Martin Blumenstingl
2017-03-18 12:36 ` [PATCH v2 3/3] ARM64: dts: meson-gxl: add support for the Khadas VIM board Martin Blumenstingl
[not found] ` <20170318123657.13798-1-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-03-18 12:36 ` [PATCH v2 1/3] devicetree: add vendor prefix for Khadas Martin Blumenstingl
2017-03-22 17:50 ` [PATCH v2 0/3] Khadas VIM support (Amlogic Meson GXL S905X) Kevin Hilman
2017-03-22 16:17 ` Kevin Hilman [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=m2zigdmgko.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=afaerber@suse.de \
--cc=carlo@caione.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gouwa@szwesion.com \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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).