mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Neil Armstrong <narmstrong@baylibre.com>,
	Christian Hewitt <christianshewitt@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Kevin Hilman <khilman@baylibre.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Nick Xie <nick@khadas.com>
Subject: Re: [PATCH] arm64: dts: meson: add thermal zones to meson gx devices
Date: Mon, 16 Mar 2020 15:36:14 +0100	[thread overview]
Message-ID: <4772a180-11d2-2806-dad7-9a0d27e5b414@linaro.org> (raw)
In-Reply-To: <90c9133e-3a56-d6d6-abf0-9a3c269bc54a@baylibre.com>

On 16/03/2020 09:20, Neil Armstrong wrote:
> On 16/03/2020 04:20, Christian Hewitt wrote:
>> Adapt and update current VIM2 thermal zones support so that zones are
>> available on all meson GXBB/GXL/GXM devices - similar to changes made
>> for G12A/G12B/SM1 devices.
>>
>> Suggested-by: Nick Xie <nick@khadas.com>
>> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
>> ---

[ ... ]

Please trim :)

> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>



-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2020-03-16 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  3:20 Christian Hewitt
2020-03-16  8:20 ` Neil Armstrong
2020-03-16 14:36   ` Daniel Lezcano [this message]
2020-03-16 17:01 ` patchwork-bot+linux-amlogic

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=4772a180-11d2-2806-dad7-9a0d27e5b414@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=christianshewitt@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=narmstrong@baylibre.com \
    --cc=nick@khadas.com \
    --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

all inboxes | Powered by JetHome®