From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Simon Horman <horms@verge.net.au>
Cc: Eduardo Valentin <edubezval@gmail.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [1/2] arm64: dts: r8a7795: add thermal cooling management
Date: Wed, 3 Jan 2018 01:03:52 +0100 [thread overview]
Message-ID: <20180103000352.GB22490@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20180102091944.py647jheghud7sl2@verge.net.au>
Hi Simon,
On 2018-01-02 10:19:44 +0100, Simon Horman wrote:
> On Mon, Jan 01, 2018 at 10:13:35AM -0800, Eduardo Valentin wrote:
> > On Wed, Sep 13, 2017 at 12:59:08PM +0200, Niklas Söderlund wrote:
> > > Add nodes and properties for thermal cooling management support.
> > >
> > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> > > ---
> >
> > Just a reminder, this series should go via your arch tree. You may add
> > my acks.
>
> Ack.
>
> Niklas, could you comment on the readiness of these patches
> for the renesas tree?
I think maybe the patches might have became a bit outdated since they
where posted due to all reg property fixup patches. The blocker for me
reposting this series is that the patches this depends
'topic/rcar-gen3-cpufreq' on are not yet in the renesas tree next or
devel branches. Do you think it would be valuable for me to refresh
these patches before the dependencies are picked up?
--
Regards,
Niklas Söderlund
next prev parent reply other threads:[~2018-01-03 0:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 10:59 [PATCH 0/2] arm64: dts: r8a7795: r8a7796: add thermal cooling management Niklas Söderlund
[not found] ` <20170913105909.13230-1-niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>
2017-09-13 10:59 ` [PATCH 1/2] arm64: dts: r8a7795: " Niklas Söderlund
[not found] ` <20170913105909.13230-2-niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>
2018-01-01 18:12 ` [1/2] " Eduardo Valentin
2018-01-01 18:13 ` Eduardo Valentin
2018-01-02 9:19 ` Simon Horman
2018-01-03 0:03 ` Niklas Söderlund [this message]
2018-01-03 10:14 ` Simon Horman
2018-01-03 10:25 ` Geert Uytterhoeven
2018-01-04 16:53 ` Simon Horman
2017-09-13 10:59 ` [PATCH 2/2] arm64: dts: r8a7796: " Niklas Söderlund
2018-01-01 18:11 ` [2/2] " Eduardo Valentin
2017-09-15 7:37 ` [PATCH 0/2] arm64: dts: r8a7795: " Simon Horman
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=20180103000352.GB22490@bigcity.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=horms@verge.net.au \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).