From: Lv Zheng <lv.zheng@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>
Cc: Lv Zheng <lv.zheng@intel.com>, Lv Zheng <zetalog@gmail.com>,
linux-acpi@vger.kernel.org
Subject: [PATCH 0/5] ACPI/EC: Cleanup debugging messages and coding styles.
Date: Tue, 14 Oct 2014 14:23:33 +0800 [thread overview]
Message-ID: <cover.1413267704.git.lv.zheng@intel.com> (raw)
This patchset contains trivial cleanup code to make it easier to search in
the EC debugging messages.
It also includes a patch to correct coding style issues that detected by
recent scripts/checkpatch.pl.
No functional changes. This patchset can only make remote debugging more
efficient.
Lv Zheng (5):
ACPI/EC: Add CPU ID to debugging messages.
ACPI/EC: Enhance the logs to apply to QR_EC transactions.
ACPI/EC: Add detailed command/query debugging information.
ACPI/EC: Refine event/query debugging messages.
ACPI/EC: Cleanup coding style.
drivers/acpi/ec.c | 109 ++++++++++++++++++++++++++++++++++-------------------
1 file changed, 70 insertions(+), 39 deletions(-)
--
1.7.10
next reply other threads:[~2014-10-14 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 6:23 Lv Zheng [this message]
2014-10-14 6:23 ` [PATCH 1/5] ACPI/EC: Add CPU ID to debugging messages Lv Zheng
2014-10-14 6:23 ` [PATCH 2/5] ACPI/EC: Enhance the logs to apply to QR_EC transactions Lv Zheng
2014-10-14 6:23 ` [PATCH 3/5] ACPI/EC: Add detailed command/query debugging information Lv Zheng
2014-10-14 6:23 ` [PATCH 4/5] ACPI/EC: Refine event/query debugging messages Lv Zheng
2014-10-14 6:24 ` [PATCH 5/5] ACPI/EC: Cleanup coding style Lv Zheng
2014-10-21 13:28 ` Rafael J. Wysocki
2014-10-22 5:05 ` Zheng, Lv
2014-10-22 5:59 ` Zheng, Lv
2014-10-22 14:10 ` Rafael J. Wysocki
2014-10-21 13:26 ` [PATCH 0/5] ACPI/EC: Cleanup debugging messages and coding styles Rafael J. Wysocki
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=cover.1413267704.git.lv.zheng@intel.com \
--to=lv.zheng@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=zetalog@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.