From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Carlo Caione <carlo@caione.org>,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: meson: libretech: update board model
Date: Wed, 12 Sep 2018 21:12:12 -0700 [thread overview]
Message-ID: <7h8t46xcgz.fsf@baylibre.com> (raw)
In-Reply-To: <20180830105317.9337-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Thu, 30 Aug 2018 12:53:17 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> There is actually several different libretech board with the CC suffix
> so the model name is not appropriate here. Update to something more
> specific
>
> Reported-by: Da Xue <da@lessconfused.com>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
Applied to v4.20/dt64
Kevin
prev parent reply other threads:[~2018-09-13 4:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 10:53 [PATCH] arm64: dts: meson: libretech: update board model Jerome Brunet
2018-09-13 4:12 ` 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=7h8t46xcgz.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=carlo@caione.org \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).