From: Len Brown <lenb@kernel.org>
To: "Tang, Feng" <feng.tang@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: ACPICA release 20120816 linuxized patches
Date: Fri, 21 Sep 2012 00:29:14 -0400 [thread overview]
Message-ID: <505BED1A.4000804@kernel.org> (raw)
In-Reply-To: <A74E4C03C808B649AF1F11527F2D44140335DA78@SHSMSX101.ccr.corp.intel.com>
Thanks for the series, Feng.
We are not doing as well here on checkpatch.pl compliance as I'd like --
something perhaps we can improve going forward?
thanks,
-Len
On 08/21/2012 10:42 PM, Tang, Feng wrote:
> Hi Len,
>
> Here are the 20120816 ACPICA linuxized patches based on
> your acpi/next branch, please review.
>
> [PATCH 01/12] ACPI: delelte more BFS/GTS related definition and code
> [PATCH 02/12] ACPICA: Enable Scope change to root during module-level code execution.
> [PATCH 03/12] ACPICA: Split ACPICA initialization functions to new file, utxfinit.c
> [PATCH 04/12] ACPICA: Comment update: Fix some typos in actble.h
> [PATCH 05/12] ACPICA: Add Windows8/Server2012 string for _OSI method.
> [PATCH 06/12] ACPICA: GPE Support: Update debug info for GPE tracing.
> [PATCH 07/12] ACPICA: Debug output: Update output for Processor object.
> [PATCH 08/12] ACPICA: GPE support: Remove extraneous parameter from low-level function.
> [PATCH 09/12] ACPICA: Headers: Add support for CSRT and DBG2 ACPI tables.
> [PATCH 10/12] ACPICA: Add support for complex _PLD buffers.
> [PATCH 11/12] ACPICA: Add struct header support for _FDE, _GRT, _GTM, and _SRT names.
> [PATCH 12/12] ACPICA: Update version to 20120816.
>
> Thanks,
> Feng
>
next prev parent reply other threads:[~2012-09-21 4:29 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
2012-08-22 2:42 ` ACPICA release 20120816 " Tang, Feng
2012-09-21 4:29 ` Len Brown [this message]
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=505BED1A.4000804@kernel.org \
--to=lenb@kernel.org \
--cc=feng.tang@intel.com \
--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).