From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Xiaoguang Chen <chenxg@marvell.com>,
Stratos Karafotis <stratosk@semaphore.gr>,
Andreas Schwab <schwab@linux-m68k.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Amit Kucheria <amit.kucheria@linaro.org>,
stable@vger.kernel.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: Potential cpufreq backports for v3.10 LTS
Date: Tue, 7 Oct 2014 15:56:24 -0700 [thread overview]
Message-ID: <20141007225624.GA8171@kroah.com> (raw)
In-Reply-To: <20141007225006.GM4609@sirena.org.uk>
On Tue, Oct 07, 2014 at 11:50:06PM +0100, Mark Brown wrote:
> On Tue, Oct 07, 2014 at 02:58:07PM -0700, Greg Kroah-Hartman wrote:
> > On Tue, Oct 07, 2014 at 09:45:05PM +0100, Mark Brown wrote:
>
> > > Actually I thinkoed here, as I said in reply to the stable mail the
> > > problematic patch was "19c763031acb8 cpufreq: serialize calls to
> > > __cpufreq_governor()" which was reverted in "56d07db cpufreq: Remove
> > > temporary fix for race between CPU hotplug and sysfs-writes". The above
> > > commit ID (95731eb) should be good.
>
> > > Sorry about the confusion here.
>
> > Ok, I'm still confused. I've applied 3 patches to the 3.10-stable
> > queue, in this order:
>
> To the best of my ability to assess:
>
> > 19c763031acb831a5ab9c1a701b7fedda073eb3f cpufreq: serialize calls to __cpufreq_governor()
>
> This one is bad.
Ok, now deleted, thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2014-10-07 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 11:48 Potential cpufreq backports for v3.10 LTS Mark Brown
2014-10-07 12:14 ` Mark Brown
2014-10-07 16:46 ` Greg Kroah-Hartman
2014-10-07 17:08 ` Mark Brown
2014-10-07 20:04 ` Greg Kroah-Hartman
2014-10-07 20:45 ` Mark Brown
2014-10-07 21:58 ` Greg Kroah-Hartman
2014-10-07 22:50 ` Mark Brown
2014-10-07 22:56 ` Greg Kroah-Hartman [this message]
2014-10-07 21:36 ` Stratos Karafotis
2014-10-07 23:07 ` Mark Brown
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=20141007225624.GA8171@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.kucheria@linaro.org \
--cc=broonie@kernel.org \
--cc=chenxg@marvell.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=schwab@linux-m68k.org \
--cc=stable@vger.kernel.org \
--cc=stratosk@semaphore.gr \
--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 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).