From: Scot Doyle <lkml14@scotdoyle.com>
To: "Zheng, Lv" <lv.zheng@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ACPI / EC: Remove non-standard log emphasis
Date: Wed, 25 Feb 2015 15:01:08 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.11.1502251459001.14861@localhost> (raw)
In-Reply-To: <1AE640813FDE7649BE1B193DEA596E88026D8057@SHSMSX101.ccr.corp.intel.com>
On Wed, 25 Feb 2015, Zheng, Lv wrote:
...
> > I was using "+++++"/"#####"/"*****" to filter different EC log entries which makes debugging easier.
> > And, if we changed this from pr_info into pr_debug, then we will have nothing in the suspend/resume logs for the EC device.
> > While there are plenty of such log entries for each of other devices.
> > So I really doubt what's the meaning of such a change.
> > Could it improve anything or just make debugging more difficult for developers?
>
> IMO, it's better to introduce such kind of code in the head of ec.c:
>
> #ifdef DEBUG_FILTER
> #define EC_LOG_DEV "+++++"
> #define EC_LOG_CMD "*****"
> #define EC_LOG_EVT "#####"
> ...
> #else
> #define EC_LOG_DEV
> #define EC_LOG_CMD
> #define EC_LOG_EVT
> #endif
>
> And wrap the pr_info, pr_debug using filter enabled new macros - ec_info, ec_debug so that we won't see the filters in the normal dmesg output and the filters are still available for the developers.
>
> Thanks and best regards
> -Lv
I agree, would you be willing to submit it?
next prev parent reply other threads:[~2015-02-25 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 19:43 [PATCH] ACPI / EC: Remove non-standard log emphasis Scot Doyle
2015-02-18 6:18 ` Rafael J. Wysocki
2015-02-25 8:41 ` Zheng, Lv
2015-02-25 8:51 ` Zheng, Lv
2015-02-25 15:01 ` Scot Doyle [this message]
2015-02-25 22:55 ` Rafael J. Wysocki
2015-02-27 0:30 ` Zheng, Lv
2015-02-27 6:48 ` [PATCH 0/2] ACPI / EC: Enhance logging/debugging Lv Zheng
2015-02-27 6:48 ` [PATCH 1/2] ACPI / EC: Cleanup logging/debugging splitter support Lv Zheng
2015-03-12 22:33 ` Joe Perches
2015-02-27 6:48 ` [PATCH 2/2] ACPI / EC: Add GPE reference counting debugging messages Lv Zheng
2015-03-12 22:42 ` [PATCH 0/2] ACPI / EC: Enhance logging/debugging 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=alpine.LNX.2.11.1502251459001.14861@localhost \
--to=lkml14@scotdoyle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
/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).