public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg@redhat.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Lin, Ming M" <ming.m.lin@intel.com>,
	linux-acpi@vger.kernel.org, mjg@redhat.com
Subject: [PATCH 0/3] acpica: Rewrite GPE handling
Date: Mon, 9 Nov 2009 22:20:03 +0000	[thread overview]
Message-ID: <20091109222003.GA3424@srcf.ucam.org> (raw)
In-Reply-To: <4911F71203A09E4D9981D27F9D830858376D905E@orsmsx503.amr.corp.intel.com>

This is a rework of my original set of GPE rework patches. The principle 
difference is that I've readded the scan of _PWR methods in the initial 
GPE parsing - though there's little distinction between runtime and 
wakeup GPEs after this patchset (other than whether they can wake the 
system), it's still necessary to do this in order to retain the existing 
behaviour of enabling all GPEs with methods *except* for those that are 
able to wake the system.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

       reply	other threads:[~2009-11-09 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4911F71203A09E4D9981D27F9D83085837684E6D@orsmsx503.amr.corp.intel.com>
     [not found] ` <20090916145517.GA24333@srcf.ucam.org>
     [not found]   ` <4911F71203A09E4D9981D27F9D830858376D879E@orsmsx503.amr.corp.intel.com>
     [not found]     ` <20090916164448.GA26552@srcf.ucam.org>
     [not found]       ` <7276C2EDBEF0FA4AAA4A8FAD7DE3436531596BE0@orsmsx503.amr.corp.intel.com>
     [not found]         ` <4911F71203A09E4D9981D27F9D830858376D905E@orsmsx503.amr.corp.intel.com>
2009-11-09 22:20           ` Matthew Garrett [this message]
2009-11-09 22:29             ` [PATCH 1/3] ACPI: Add infrastructure for refcounting GPE consumers Matthew Garrett
2009-11-09 22:29               ` [PATCH 2/3] ACPI: Add support for new refcounted GPE API to drivers Matthew Garrett
2009-11-09 22:29                 ` [PATCH 3/3] ACPI: Remove old GPE API and transition code entirely to new one Matthew Garrett

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=20091109222003.GA3424@srcf.ucam.org \
    --to=mjg@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=robert.moore@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox