From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
linux-pm@lists.linux-foundation.org, linux-acpi@vger.kernel.org,
Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Jean Pihet <j-pihet@ti.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Kevin Hilman <khilman@ti.com>, Arnd Bergmann <arnd@arndb.de>,
Ferenc Wagner <wferi@niif.hu>, "Tomas M." <tmezzadra@gmail.com>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
preeti@linux.vnet.ibm.com
Subject: Re: [PATCH] ACPI, cpuidle: Fix suspend/resume regression caused by cpuidle cleanup.
Date: Wed, 13 Jun 2012 10:25:12 -0700 [thread overview]
Message-ID: <4FD8CCF8.1000607@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FD87249.6010302@linux.vnet.ibm.com>
On 06/13/2012 03:58 AM, Deepthi Dharwar wrote:
> In addition to the above fix, a sanity check has also been added
> in x86 arch specific cpu_idle call to ensure that the idle call
> always returns with IRQs enabled.
>
> This patch applies on 3.5-rc2
Just applied this on top of a post-3.5-rc2 kernel (7794f70).
Suspend/resume seems to work just fine on the hardware where it was
broken. Thanks, Deepthi!
My tested-by was for the original hackish patch, but this is just to
spell out that it worked for me with this patch too.
Tested-by: Dave Hansen <dave@linux.vnet.ibm.com>
next prev parent reply other threads:[~2012-06-13 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 10:58 [PATCH] ACPI, cpuidle: Fix suspend/resume regression caused by cpuidle cleanup Deepthi Dharwar
2012-06-13 17:25 ` Dave Hansen [this message]
2012-06-13 20:01 ` Rafael J. Wysocki
2012-06-15 12:16 ` Deepthi Dharwar
2012-06-15 12:25 ` Deepthi Dharwar
2012-06-15 12:25 ` Deepthi Dharwar
2012-06-15 12:27 ` Deepthi Dharwar
2012-06-16 13:36 ` Rafael J. Wysocki
2012-06-19 20:35 ` Rafael J. Wysocki
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=4FD8CCF8.1000607@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=arjan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=deepthi@linux.vnet.ibm.com \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-pm@vger.kernel.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tmezzadra@gmail.com \
--cc=wferi@niif.hu \
/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.