public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: "Moore, Robert" <robert.moore@intel.com>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: ACPICA Release 20090730 linuxized patches
Date: Fri, 14 Aug 2009 09:58:04 +0800	[thread overview]
Message-ID: <1250215084.2987.7.camel@minggr.sh.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]

Hi, Len

ACPICA Release 20090730 linuxized patches attached.
Build&Test on 32&64 bit machines.

Applied cleanly on top of linux-acpi-2.6/test branch.

Lin Ming
---
[PATCH 01/13] ACPICA: Move predefined repair code to new file, no functional change
[PATCH 02/13] ACPICA: Add repair for predefined methods that return nested packages
[PATCH 03/13] ACPICA: ACPI 4.0 : Add new return package type, restructure module.
[PATCH 04/13] ACPICA: Fix fault if acpi_terminate is called twice
[PATCH 05/13] ACPICA: Split large ACPI table header
[PATCH 06/13] ACPICA: ACPI 4: Update headers for new and changed ACPI tables.
[PATCH 07/13] ACPICA: reformat predefined method table, no functional change
[PATCH 08/13] ACPICA: ACPI 4: Add validation for new predefined names.
[PATCH 09/13] ACPICA: Add support for module-level executable AML code
[PATCH 10/13] ACPICA: Update definitions for HEST table
[PATCH 11/13] ACPICA: Fix typo for HEST ACPI table
[PATCH 12/13] ACPICA: acpi_reset: Bypass port validation mechanism
[PATCH 13/13] ACPICA: Update version to 20090730

[-- Attachment #2: acpica-v20090730.mbox.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 29083 bytes --]

             reply	other threads:[~2009-08-14  2:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14  1:58 Lin Ming [this message]
2009-08-15  3:30 ` ACPICA Release 20090730 linuxized patches Len Brown
2009-08-17  1:40   ` Lin Ming
2009-08-15  3:33 ` Len Brown
2009-08-17  2:04   ` Lin Ming
2009-08-17  2:11     ` Lin Ming
2009-08-28 23:41       ` 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=1250215084.2987.7.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