From: Eduardo Valentin <edubezval@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Rafael Wysocki <rjw@rjwysocki.net>,
linux-arm-kernel@lists.infradead.org,
Russell King <rmk+kernel@arm.linux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH V2] thermal: cpu_cooling: fix lockdep problems in cpu_cooling
Date: Fri, 14 Aug 2015 18:10:16 -0700 [thread overview]
Message-ID: <20150815011015.GA4125@localhost.localdomain> (raw)
In-Reply-To: <20150814055556.GZ20238@linux>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On Fri, Aug 14, 2015 at 11:25:56AM +0530, Viresh Kumar wrote:
> On 12-08-15, 15:22, Viresh Kumar wrote:
> > From: Russell King <rmk+kernel@arm.linux.org.uk>
> > Fixes: 2dcd851fe4b4 ("thermal: cpu_cooling: Update always cpufreq policy with
> > Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> >
> > Hi Eduardo/Zhang,
> >
> > This is 4.2-rc material, please apply soon.
>
> Hey,
>
> Please apply this one and drop
>
> 8ad61f934e9e ("thermal: cpu_cooling: fix lockdep problems in
> cpu_cooling")
OK, I am having a looking at this.
>
> --
> viresh
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: edubezval@gmail.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] thermal: cpu_cooling: fix lockdep problems in cpu_cooling
Date: Fri, 14 Aug 2015 18:10:16 -0700 [thread overview]
Message-ID: <20150815011015.GA4125@localhost.localdomain> (raw)
In-Reply-To: <20150814055556.GZ20238@linux>
On Fri, Aug 14, 2015 at 11:25:56AM +0530, Viresh Kumar wrote:
> On 12-08-15, 15:22, Viresh Kumar wrote:
> > From: Russell King <rmk+kernel@arm.linux.org.uk>
> > Fixes: 2dcd851fe4b4 ("thermal: cpu_cooling: Update always cpufreq policy with
> > Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> >
> > Hi Eduardo/Zhang,
> >
> > This is 4.2-rc material, please apply soon.
>
> Hey,
>
> Please apply this one and drop
>
> 8ad61f934e9e ("thermal: cpu_cooling: fix lockdep problems in
> cpu_cooling")
OK, I am having a looking at this.
>
> --
> viresh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150814/7b2c8ec3/attachment.sig>
next prev parent reply other threads:[~2015-08-15 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:52 [PATCH V2] thermal: cpu_cooling: fix lockdep problems in cpu_cooling Viresh Kumar
2015-08-12 9:52 ` Viresh Kumar
2015-08-12 9:52 ` Viresh Kumar
2015-08-14 5:55 ` Viresh Kumar
2015-08-14 5:55 ` Viresh Kumar
2015-08-15 1:10 ` Eduardo Valentin [this message]
2015-08-15 1:10 ` Eduardo Valentin
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=20150815011015.GA4125@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rui.zhang@intel.com \
--cc=viresh.kumar@linaro.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 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.