All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.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 21:45:05 +0100	[thread overview]
Message-ID: <20141007204505.GL4609@sirena.org.uk> (raw)
In-Reply-To: <20141007200458.GA12028@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On Tue, Oct 07, 2014 at 01:04:58PM -0700, Greg Kroah-Hartman wrote:
> On Tue, Oct 07, 2014 at 06:08:00PM +0100, Mark Brown wrote:

> > > >  - 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 :(

> > Interesting, I was able to cherry-pick it...  looks like the upstream
> > version is 95731eb.  In any case at roughly the same time you sent your
> > mail it's been drawn to my attention off-list that this was subsequently
> > reverted so please ignore this one.  The others should be fine though.

> Ok, I've queued the others up now.

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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-10-07 20:45 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 [this message]
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=20141007204505.GL4609@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=amit.kucheria@linaro.org \
    --cc=chenxg@marvell.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=gregkh@linuxfoundation.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.