From: Zhang Rui <rui.zhang@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Eduardo Valentin <edubezval@gmail.com>,
robh@kernel.org, Wei Xu <xuwei5@hisilicon.com>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
devicetree@vger.kernel.org, olof@lixom.net,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] dt: thermal: Fix broken cooling-maps
Date: Mon, 06 Aug 2018 14:29:38 +0800 [thread overview]
Message-ID: <1533536978.2158.86.camel@intel.com> (raw)
In-Reply-To: <20180803084000.73ofs6cttnqc6uiq@vireshk-i7>
On 五, 2018-08-03 at 14:10 +0530, Viresh Kumar wrote:
> On 31-07-18, 14:00, Zhang Rui wrote:
> >
> > I suppose this patch should go via Eduardo' tree.
> > Eduardo, can you please take a look at this patch set?
> Zhang,
>
> Since Eduardo isn't replying, will it be possible for you to pick it
> up as I
> don't want to miss 4.19-rc1.
>
Okay, I will keep queue it in my tree first.
thanks,
rui
WARNING: multiple messages have this Message-ID (diff)
From: rui.zhang@intel.com (Zhang Rui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] dt: thermal: Fix broken cooling-maps
Date: Mon, 06 Aug 2018 14:29:38 +0800 [thread overview]
Message-ID: <1533536978.2158.86.camel@intel.com> (raw)
In-Reply-To: <20180803084000.73ofs6cttnqc6uiq@vireshk-i7>
On ?, 2018-08-03 at 14:10 +0530, Viresh Kumar wrote:
> On 31-07-18, 14:00, Zhang Rui wrote:
> >
> > I suppose this patch should go via Eduardo' tree.
> > Eduardo, can you please take a look at this patch set?
> Zhang,
>
> Since Eduardo isn't replying, will it be possible for you to pick it
> up as I
> don't want to miss 4.19-rc1.
>
Okay, I will keep queue it in my tree first.
thanks,
rui
next prev parent reply other threads:[~2018-08-06 6:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 5:09 [PATCH 0/2] dt: thermal: Fix broken cooling-maps Viresh Kumar
2018-07-05 5:09 ` Viresh Kumar
2018-07-05 5:09 ` [PATCH 1/2] dt-bindings: thermal: Allow multiple devices to share cooling map Viresh Kumar
2018-07-16 4:34 ` Viresh Kumar
2018-07-16 22:02 ` Rob Herring
2018-07-05 5:09 ` [PATCH 2/2] arm64: dts: hi6220: Add all CPUs in cooling maps Viresh Kumar
2018-07-05 5:09 ` Viresh Kumar
2018-07-05 8:44 ` Daniel Lezcano
2018-07-05 8:44 ` Daniel Lezcano
2018-07-17 10:54 ` [PATCH] of: thermal: Allow multiple devices to share cooling map Viresh Kumar
2018-08-06 18:05 ` Eduardo Valentin
2018-08-08 7:08 ` [PATCH V2] " Viresh Kumar
2018-08-24 23:14 ` Eduardo Valentin
2018-07-18 15:34 ` [PATCH 0/2] dt: thermal: Fix broken cooling-maps Wei Xu
2018-07-18 15:34 ` Wei Xu
2018-07-18 15:34 ` Wei Xu
2018-07-19 2:40 ` Viresh Kumar
2018-07-19 2:40 ` Viresh Kumar
2018-07-19 9:54 ` Wei Xu
2018-07-19 9:54 ` Wei Xu
2018-07-19 9:54 ` Wei Xu
2018-07-31 4:51 ` Viresh Kumar
2018-07-31 4:51 ` Viresh Kumar
2018-07-31 6:00 ` Zhang Rui
2018-07-31 6:00 ` Zhang Rui
2018-08-03 8:40 ` Viresh Kumar
2018-08-03 8:40 ` Viresh Kumar
2018-08-06 6:29 ` Zhang Rui [this message]
2018-08-06 6:29 ` Zhang Rui
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=1533536978.2158.86.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=xuwei5@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.