From: Lin Ming <ming.m.lin@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>
Subject: ACPICA release 20091214 linuxized patch
Date: Tue, 15 Dec 2009 13:12:25 +0800 [thread overview]
Message-ID: <1260853945.3834.48.camel@minggr.sh.intel.com> (raw)
Hi, Len
ACPICA release 20091214 linuxized patch attached.
Applied cleanly on top of Linus' tree.
Build and test on 32&64 bit machines.
[PATCH 01/16] ACPICA: Fix possible memory leak for module-level code execution
[PATCH 02/16] ACPICA: Fix two Scope type error messages
[PATCH 03/16] ACPICA: Fix two additional Scope override error messages
[PATCH 04/16] ACPICA: Add repair for bad _FDE/_GTM buffers
[PATCH 05/16] ACPICA: Update internal namespace node/handle interfaces
[PATCH 06/16] ACPICA: Add more conversions to predefined name repair module
[PATCH 07/16] ACPICA: Update function headers, no functional change
[PATCH 08/16] ACPICA: Fix mutex errors when running _REG methods
[PATCH 09/16] ACPICA: Move Package-to-Buffer repair code into common ToBuffer function
[PATCH 10/16] ACPICA: Remove messages if predefined repair(s) are successful
[PATCH 11/16] ACPICA: Update function headers and comments, no functional change
[PATCH 12/16] ACPICA: Conditionally perform complex per-predefined-name repairs
[PATCH 13/16] ACPICA: Module-level code: enable _REG execution in same scope
[PATCH 14/16] ACPICA: Predefined name repair: automatically remove null package elements
[PATCH 15/16] ACPICA: Move check for valid Thread ID structure
[PATCH 16/16] ACPICA: Update version to 20091214
Lin Ming
next reply other threads:[~2009-12-15 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 5:12 Lin Ming [this message]
2009-12-15 5:13 ` ACPICA release 20091214 linuxized patch Lin Ming
2009-12-15 22:30 ` 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=1260853945.3834.48.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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