From: Lin Ming <ming.m.lin@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>, Len Brown <lenb@kernel.org>,
Bob Moore <robert.moore@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: [PATCH 0/6] Minimize ACPICA/linux GPE code divergence
Date: Mon, 06 Dec 2010 23:58:15 +0800 [thread overview]
Message-ID: <1291651095.2197.78.camel@localhost> (raw)
Hi, Rafael
We have ported below of your GPE patches into ACPICA code base.
0001-ACPI-ACPICA-Do-not-execute-_PRW-methods-during-initi.patch
0002-ACPI-ACPICA-Fail-acpi_gpe_wakeup-if-ACPI_GPE_CAN_WAK.patch
0003-ACPI-ACPICA-Simplify-acpi_ev_initialize_gpe_block.patch
0004-ACPI-ACPICA-Fix-reference-counting-problems-with-GPE.patch
0005-ACPI-ACPICA-Defer-enabling-of-runtime-GPEs-v3.patch
You can find the ACPICA port at,
http://git.moblin.org/cgit.cgi/acpica/commit/?id=3bc77e86ae03b3ceb7241f224053e399fb3f56b2
As the port, some changes were made, function and variable renamed, etc,
and new features were added, implicit notify, global event handler, etc.
These changes and new features introduce a lot of ACPICA/linux GPE code
divergence. So this series of patches is to minimize this type of
divergence.
[PATCH 1/6] ACPICA: Move GPE functions to new file evxfgpe.c
[PATCH 2/6] ACPICA: Rename some function and variable names
[PATCH 3/6] ACPICA: Remove unused function declarations
[PATCH 4/6] ACPICA: Implicit notify support
[PATCH 5/6] ACPICA: Global event handler
[PATCH 6/6] ACPICA: Misc comments to minimize code divergence
Thanks for any comments.
Lin Ming
reply other threads:[~2010-12-06 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1291651095.2197.78.camel@localhost \
--to=ming.m.lin@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 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.