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 09:46:43 -0700 [thread overview]
Message-ID: <20141007164643.GA3748@kroah.com> (raw)
In-Reply-To: <20141007114844.GT4609@sirena.org.uk>
On Tue, Oct 07, 2014 at 12:48:44PM +0100, Mark Brown wrote:
> Hi,
>
> The power management team at Linaro has had a look at the cpufreq
> updates since the v3.10 LTS and identified a few patches that look
> like they should be in there. The most recent of these is from v3.12 so
> they won't apply to any of the more recent stable kernels.
>
> - 59a6342203a7a cpufreq: Fix governor start/stop race condition
>
> This looks like a straight race condition fix.
That is not a commit id in Linus's tree :(
next prev parent reply other threads:[~2014-10-07 16:46 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 [this message]
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
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=20141007164643.GA3748@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 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.