From: Len Brown <lenb@kernel.org>
To: Feng Tang <feng.tang@intel.com>
Cc: len.brown@intel.com, linux-acpi@vger.kernel.org, mjg@redhat.com,
tianyu.lan@intel.com, gregkh@linuxfoundation.org,
Bob Moore <robert.moore@intel.com>
Subject: Re: [PATCH V2 1/2] ACPI: Use ACPICA native way to decode the PLD buffer
Date: Fri, 21 Sep 2012 00:32:17 -0400 [thread overview]
Message-ID: <505BEDD1.4000802@kernel.org> (raw)
In-Reply-To: <20120822163523.2b0199bb@feng-i7>
applied to acpica branch.
thanks,
-Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2012-09-21 4:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 6:24 [PATCH 1/2] ACPI: Use ACPICA native way to decode the PLD buffer Feng Tang
2012-08-22 6:24 ` [PATCH 2/2] usb-acpi: Comply with the ACPI API change Feng Tang
2012-08-22 7:05 ` [PATCH 1/2] ACPI: Use ACPICA native way to decode the PLD buffer Lan Tianyu
2012-08-22 7:16 ` Feng Tang
2012-08-22 8:35 ` [PATCH V2 " Feng Tang
2012-09-21 4:32 ` 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=505BEDD1.4000802@kernel.org \
--to=lenb@kernel.org \
--cc=feng.tang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=robert.moore@intel.com \
--cc=tianyu.lan@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).