public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, stable@kernel.org,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [git pull request] ACPI patches for Linux 2.6.36-rc6
Date: Fri, 1 Oct 2010 23:08:12 +0200	[thread overview]
Message-ID: <201010012308.12897.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.1010010142470.7033@localhost.localdomain>

On Friday, October 01, 2010, Len Brown wrote:
> Hi Linus,
> 
> please pull from: 
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release
> 
...
> commit 573b638158029898caf9470c8214b7ddd29751e3
> Author: Colin Ian King <colin.king@canonical.com>
> Date:   Mon Aug 2 15:14:43 2010 +0000

This one should go to -stable, shouldn't it?

>     ACPI: enable repeated PCIEXP wakeup by clearing PCIEXP_WAKE_STS on resume
>     
>     Section 4.7.3.1.1 (PM1 Status Registers) of version 4.0 of
>     the ACPI spec concerning PCIEXP_WAKE_STS points out in
>     in the final note field in table 4-11 that if this bit is
>     set to 1 and the system is put into a sleeping state then
>     the system will not automatically wake.
>     
>     This bit gets set by hardware to indicate that the system
>     woke up due to a PCI Express wakeup event, so clear it during
>     acpi_hw_clear_acpi_status() calls to enable subsequent
>     resumes to work.
>     
>     BugLink: http://bugs.launchpad.net/bugs/613381
>     
>     Signed-off-by: Colin Ian King <colin.king@canonical.com>
>     Signed-off-by: Len Brown <len.brown@intel.com>

Thanks,
Rafael

  reply	other threads:[~2010-10-01 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  5:45 [git pull request] ACPI patches for Linux 2.6.36-rc6 Len Brown
2010-10-01 21:08 ` Rafael J. Wysocki [this message]
2010-10-01 23:31   ` Len 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=201010012308.12897.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=gregkh@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox