All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	khilman@deeprootsystems.com, venkatesh.pallipadi@intel.com,
	linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	lenb@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] CPUidle: always return with interrupts enabled
Date: Fri, 16 Oct 2009 17:25:04 +0100	[thread overview]
Message-ID: <20091016162504.GC1391@deprecation.cyrius.com> (raw)
In-Reply-To: <20091006133456.5177a32a.akpm@linux-foundation.org>

* 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>

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

Reference with the patch: http://patchwork.kernel.org/patch/50728/
-- 
Martin Michlmayr
http://www.cyrius.com/

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 17:35 [PATCH] CPUidle: always return with interrupts enabled Kevin Hilman
2009-09-30 21:21 ` Rafael J. Wysocki
2009-09-30 21:21 ` Rafael J. Wysocki
2009-10-06 20:34   ` Andrew Morton
2009-10-06 20:34     ` Andrew Morton
2009-10-06 21:02     ` Kevin Hilman
2009-10-06 21:02       ` Kevin Hilman
2009-10-16 16:25     ` Martin Michlmayr [this message]
2009-10-16 21:11       ` Andrew Morton
2009-10-16 21:11         ` Andrew Morton
2009-10-16 16:25     ` Martin Michlmayr
  -- strict thread matches above, loose matches on Subject: below --
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=20091016162504.GC1391@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=akpm@linux-foundation.org \
    --cc=khilman@deeprootsystems.com \
    --cc=lenb@kernel.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=rjw@sisk.pl \
    --cc=venkatesh.pallipadi@intel.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 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.