public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Lin Ming <ming.m.lin@intel.com>
Cc: "Moore, Robert" <robert.moore@intel.com>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: ACPICA Release 20100331 linuxized patches
Date: Tue, 20 Apr 2010 10:51:17 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1004201050330.2402@sony> (raw)
In-Reply-To: <1270710730.3473.34.camel@minggr.sh.intel.com>

applied to acpi-test
(and acpica branch re-based to 2.6.34-rc5 to allow 8/9 to apply)

thanks,
Len Brown, Intel Open Source Technology Center

On Thu, 8 Apr 2010, Lin Ming wrote:

> Hi, Len
> 
> This patch series applied cleanly on top of your acpi/test branch.
> Build and test on my machine and it works well.
> 
> [PATCH 1/9] ACPICA: Update comments/headers, no functional change
> [PATCH 2/9] ACPICA: Fix for acpi_reallocate_root_table for incorrect root table copy
> [PATCH 3/9] ACPICA: Add write support for DataTable operation regions
> [PATCH 4/9] ACPICA: Add detection of corrupted/replaced DSDT
> [PATCH 5/9] ACPICA: Add subsystem option to force copy of DSDT to local memory
> [PATCH 6/9] ACPICA: Update DSDT copy/detection.
> [PATCH 7/9] ACPI: add boot option acpi=copy_dsdt to fix corrupt DSDT
> [PATCH 8/9] ACPICA: Minimize the differences between linux GPE code and ACPICA code base
> [PATCH 9/9] ACPICA: Update version to 20100331.
> 
> Patch 7 includes the acpi=copy_dsdt option, DMI backlist and customized
> ACPICA warning message for corrupt DSDT workaround (bug 14679).
> 
> Lin Ming
> 
> 

      reply	other threads:[~2010-05-01  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  7:12 ACPICA Release 20100331 linuxized patches Lin Ming
2010-04-20 14:51 ` Len Brown [this message]

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=alpine.LFD.2.00.1004201050330.2402@sony \
    --to=lenb@kernel.org \
    --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