All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: stable <stable@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix 2.6.32.23 suspend regression caused by commit 6f6198a
Date: Fri, 01 Oct 2010 21:44:11 +0200	[thread overview]
Message-ID: <1285962251.9020.6.camel@marge.simson.net> (raw)
In-Reply-To: <20101001191611.GA5259@kroah.com>

On Fri, 2010-10-01 at 12:16 -0700, Greg KH wrote:
> On Fri, Oct 01, 2010 at 07:04:11AM +0200, Mike Galbraith wrote:
> > Again, with a less bouncy address.
> > 
> > From: Mike Galbraith <efault@gmx.de>
> > Date: Fri, 1 Oct 2010 05:57:59 +0200
> > Subject: [PATCH] fix 2.6.32.23 suspend regression caused by commit
> > 6f6198a
> > 
> > 6f6198a sched: kill migration thread in CPU_POST_DEAD instead of
> > CPU_DEAD
> > leaves migration threads lying about.  Mask out CPU_TASKS_FROZEN.
> > 
> > Signed-off-by: Mike Galbraith <efault@gmx.de>
> 
> Is this patch upstream already?  If so, what's the git commit id of it?
> If not, why isn't it also needed there?

No, it's not upstream, and will never go upstream because they don't
need it.  It's only needed for -stable because the fix incorporated in
-stable is incomplete.  Upstream already does what this patch adds.

	-Mike


  reply	other threads:[~2010-10-01 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  4:27 [PATCH] fix 2.6.32.23 suspend regression caused by commit 6f6198a Mike Galbraith
2010-10-01  5:04 ` Mike Galbraith
2010-10-01 19:16   ` Greg KH
2010-10-01 19:44     ` Mike Galbraith [this message]
2010-10-01 21:00       ` Greg KH

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=1285962251.9020.6.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.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.