From: Heiko Stuebner <heiko@sntech.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] dt-bindings: ARM: dts: rockchip: Add bindings for rk3288-veyron-{fievel,tiger}
Date: Thu, 25 Jul 2019 22:51:33 +0200 [thread overview]
Message-ID: <9603810.NFohB8vNa9@phil> (raw)
In-Reply-To: <20190725162642.250709-4-mka@chromium.org>
Am Donnerstag, 25. Juli 2019, 18:26:40 CEST schrieb Matthias Kaehlcke:
> Fievel is a Chromebox and Tiger a Chromebase with a 10" display and
> touchscreen. Tiger and Fievel are based on the same board.
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
applied for 5.4
next prev parent reply other threads:[~2019-07-25 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 16:26 [PATCH v3 0/5] Add veyron tiger and fievel boards Matthias Kaehlcke
2019-07-25 16:26 ` [PATCH v3 1/5] ARM: dts: rockchip: move rk3288-veryon display settings into a separate file Matthias Kaehlcke
2019-07-25 16:48 ` Doug Anderson
2019-07-25 20:45 ` Heiko Stuebner
2019-07-25 16:26 ` [PATCH v3 2/5] ARM: dts: rockchip: consolidate veyron panel and backlight settings Matthias Kaehlcke
2019-07-25 20:46 ` Heiko Stuebner
2019-07-25 16:26 ` [PATCH v3 3/5] dt-bindings: ARM: dts: rockchip: Add bindings for rk3288-veyron-{fievel,tiger} Matthias Kaehlcke
2019-07-25 16:53 ` Doug Anderson
2019-07-25 20:51 ` Heiko Stuebner [this message]
2019-07-25 16:26 ` [PATCH v3 4/5] ARM: dts: rockchip: add veyron-fievel board Matthias Kaehlcke
2019-07-25 20:55 ` Heiko Stuebner
2019-07-25 16:26 ` [PATCH v3 5/5] ARM: dts: rockchip: add veyron-tiger board Matthias Kaehlcke
2019-07-25 20:57 ` Heiko Stuebner
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=9603810.NFohB8vNa9@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--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).