From: Feng Tang <feng.tang@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>,
lv.zheng@intel.com
Subject: Re: ACPICA release 20120816 linuxized patches
Date: Fri, 21 Sep 2012 12:51:15 +0800 [thread overview]
Message-ID: <20120921125115.3fabde66@feng-i7> (raw)
In-Reply-To: <505BED1A.4000804@kernel.org>
Hi Len
On Fri, 21 Sep 2012 12:29:14 +0800
Len Brown <lenb@kernel.org> wrote:
> 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?
Sure, will keep that in mind. thanks,
- Feng
next prev parent reply other threads:[~2012-09-21 4:57 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
2012-09-21 4:51 ` Feng Tang [this message]
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=20120921125115.3fabde66@feng-i7 \
--to=feng.tang@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@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;
as well as URLs for NNTP newsgroup(s).