From: Lin Ming <ming.m.lin@intel.com>
To: lenb <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>,
Tang Feng <feng.tang@intel.com>
Subject: Re: ACPICA release 20120711 linuxized patches
Date: Wed, 18 Jul 2012 14:00:02 +0800 [thread overview]
Message-ID: <1342591202.31687.6.camel@minggr> (raw)
In-Reply-To: <1342415080.3628.179.camel@minggr>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Mon, 2012-07-16 at 13:04 +0800, Lin Ming wrote:
> Hi Len,
>
> ACPICA release 20120711 linuxized patches attached.
> Applied on top of your acpi/next branch.
>
> [PATCH 01/10] ACPICA: Split exception code utilities to a new file,
> [PATCH 02/10] ACPICA: Add new interfaces for BIOS(firmware) errors
> [PATCH 03/10] ACPICA: Table manager: deploy new firmware
> [PATCH 04/10] ACPICA: Fix some comment fields
> [PATCH 05/10] ACPICA: Add PCC address space to space ID decode
> [PATCH 06/10] ACPICA: Split file: tbxface.c -> tbxfload.c
> [PATCH 07/10] ACPICA: Add new ACPI table load/unload external
> [PATCH 08/10] ACPICA: Update header files copyrights to 2012
> [PATCH 09/10] ACPICA: AcpiSrc: Fix some translation issues for Linux
> [PATCH 10/10] ACPICA: Update to version 20120711
Hi Len,
Please use the attached updated patches.
PATCH 02 and 07 were updated.
In PATCH 07, sgi_hotplug.c was changed to use the new interface
acpi_unload_parent_table.
>
> Regards,
> Lin Ming
>
[-- Attachment #2: acpica-v20120711-v2.patch.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 44396 bytes --]
next prev parent reply other threads:[~2012-07-18 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 5:04 ACPICA release 20120711 linuxized patches Lin Ming
2012-07-18 6:00 ` Lin Ming [this message]
2012-08-22 2:42 ` ACPICA release 20120816 " Tang, Feng
2012-09-21 4:29 ` Len Brown
2012-09-21 4:51 ` Feng Tang
2012-09-21 5:33 ` Moore, Robert
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=1342591202.31687.6.camel@minggr \
--to=ming.m.lin@intel.com \
--cc=feng.tang@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;
as well as URLs for NNTP newsgroup(s).