public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] CPUidle: always return with interrupts enabled
Date: Fri, 16 Oct 2009 14:11:04 -0700	[thread overview]
Message-ID: <20091016141104.d794f2c4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091016162504.GC1391@deprecation.cyrius.com>

On Fri, 16 Oct 2009 17:25:04 +0100
Martin Michlmayr <tbm@cyrius.com> wrote:

> * Andrew Morton <akpm@linux-foundation.org> [2009-10-06 13:34]:
> > Rigor mortis is setting in on this one.
> 
> > The patch seems correct to me.
> 
> Can someone put this patch in now?  The problem has also been reported
> on Marvell's Kirkwood platform (ARM) by a number of users and the
> patch fixes it.
> 
> Tested-by: Martin Michlmayr <tbm@cyrius.com>

I have it in my for-2.6.32 queue.

> Please CC stable when you commit the patch since it also needs to go
> in for 2.6.31.

hm, I didn't know that.  So noted, thanks.

  parent reply	other threads:[~2009-10-16 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1254332153-23493-1-git-send-email-khilman@deeprootsystems.com>
2009-09-30 21:21 ` [PATCH] CPUidle: always return with interrupts enabled Rafael J. Wysocki
     [not found] ` <200909302321.33088.rjw@sisk.pl>
2009-10-06 20:34   ` Andrew Morton
2009-10-06 21:02     ` Kevin Hilman
2009-10-16 16:25     ` Martin Michlmayr
     [not found]     ` <20091016162504.GC1391@deprecation.cyrius.com>
2009-10-16 21:11       ` Andrew Morton [this message]
2009-09-30 17:35 Kevin Hilman

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=20091016141104.d794f2c4.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=tbm@cyrius.com \
    /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