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 20110211 linuxized patches
Date: Fri, 18 Mar 2011 18:01:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1103181756470.24304@x980> (raw)
In-Reply-To: <1300414593.29989.2.camel@minggr.sh.intel.com>
> Did you push these patches out to the linux-acpi-2.6.git repository?
yes, the've been on the acpica branch for about a month,
though strangely I don't see that branch updated on kernel.org...
will fix now.
cheers,
-Len
> Lin Ming
>
> On Mon, 2011-02-14 at 16:31 +0800, Lin Ming wrote:
> > Hi, Len
> >
> > ACPICA release 20110211 linuxized patches attached.
> > Applied cleanly on top of Linus tree(091994cf) and tested on my
> > notebook.
> >
> > [PATCH 1/9] ACPICA: GPE detect optimization - ignore unused GPE registers
> > [PATCH 2/9] ACPICA: Remove use of unreliable FADT revision field
> > [PATCH 3/9] ACPICA: Clarify a couple of error messages
> > [PATCH 4/9] ACPICA: Split large utglobal into utdecode.c.
> > [PATCH 5/9] ACPICA: Fix unresolved name issue for no-debug and no-error-msg cases
> > [PATCH 6/9] ACPICA: Split large dsopcode and dsload.c files.
> > [PATCH 7/9] ACPICA: Add support for FunctionalFixedHW in acpi_ut_get_region_name
> > [PATCH 8/9] ACPICA: Add mechanism to defer _REG methods for some installed handlers
> > [PATCH 9/9] ACPICA: Update version to 20110211.
> >
> > Lin Ming
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2011-03-18 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1297672276.21742.21.camel@minggr.sh.intel.com>
2011-03-03 0:40 ` ACPICA release 20110211 linuxized patches Len Brown
2011-03-18 2:16 ` Lin Ming
2011-03-18 22:01 ` 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.02.1103181756470.24304@x980 \
--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