From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: Hsin-Yi Wang <hsinyi@chromium.org>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Fabien Parent <fparent@baylibre.com>,
Sean Wang <sean.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, Ben Ho <Ben.Ho@mediatek.com>
Subject: Re: [PATCH v4 4/4] arm64: dts: mt8183: Add kukui-jacuzzi-juniper board
Date: Wed, 24 Mar 2021 11:58:41 +0100 [thread overview]
Message-ID: <20210324105841.anhogvmawrlpnyqy@rcn-XPS-13-9360> (raw)
In-Reply-To: <20210319035245.2751911-4-hsinyi@chromium.org>
Hi all,
On vie 19-03-2021 11:52:45, Hsin-Yi Wang wrote:
> Juniper is known as Acer Chromebook Spin 311 (CP311-3H).
>
> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
I picked this patch in the current rc4 kernel and booted it successfully
on an Acer Chromebook Spin 311 with no noticeable problems, so:
Tested-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-24 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 3:52 [PATCH v4 1/4] dt-bindings: arm64: dts: mediatek: Add mt8183-kukui-jacuzzi-damu Hsin-Yi Wang
2021-03-19 3:52 ` [PATCH v4 2/4] dt-bindings: arm64: dts: mediatek: Add mt8183-kukui-jacuzzi-juniper Hsin-Yi Wang
2021-03-19 9:06 ` Enric Balletbo i Serra
2021-03-26 1:46 ` Rob Herring
2021-03-19 3:52 ` [PATCH v4 3/4] arm64: dts: mt8183: Add kukui-jacuzzi-damu board Hsin-Yi Wang
2021-03-19 3:52 ` [PATCH v4 4/4] arm64: dts: mt8183: Add kukui-jacuzzi-juniper board Hsin-Yi Wang
2021-03-24 10:58 ` Ricardo Cañuelo [this message]
2021-03-26 1:46 ` [PATCH v4 1/4] dt-bindings: arm64: dts: mediatek: Add mt8183-kukui-jacuzzi-damu Rob Herring
2021-03-29 11:47 ` Matthias Brugger
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=20210324105841.anhogvmawrlpnyqy@rcn-XPS-13-9360 \
--to=ricardo.canuelo@collabora.com \
--cc=Ben.Ho@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=fparent@baylibre.com \
--cc=hsinyi@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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).