From: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "rjw@sisk.pl" <rjw@sisk.pl>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-dev@lists.linaro.org" <linaro-dev@lists.linaro.org>,
"patches@linaro.org" <patches@linaro.org>,
PDSW-power-team <PDSW-power-team@arm.com>,
Sudeep.KarkadaNagesha@arm.com
Subject: Re: [PATCH 2/2] cpufreq: Debugging options for the cpufreq subsystem
Date: Wed, 17 Oct 2012 10:20:58 +0100 [thread overview]
Message-ID: <507E787A.3020206@arm.com> (raw)
In-Reply-To: <bf2567a3c3b6f35c606ea8d71722048eefb0c45a.1350451100.git.viresh.kumar@linaro.org>
On 17/10/12 06:20, Viresh Kumar wrote:
> This adds Kconfig options for DEBUG and VERBOSE_DEBUG to the cpufreq subsystem,
> This is pretty useful for developers who want to debug cpufreq subsystem and
> don't want to editing the Makefile manually each time they want to debug.
>
You can easily overcome this issue using dynamic debugging.
You need not recompile the code enabling debug if CONFIG_DYNAMIC_DEBUG
is enabled.
Regards,
Sudeep
next prev parent reply other threads:[~2012-10-17 9:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 5:20 [PATCH 1/2] cpufreq: Improve debug prints Viresh Kumar
[not found] ` <3b38cb8ab136e5af3a70fceb7d77ad9fc889eb3f.1350451100.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-10-17 5:20 ` [PATCH 2/2] cpufreq: Debugging options for the cpufreq subsystem Viresh Kumar
2012-10-17 5:20 ` Viresh Kumar
2012-10-17 9:20 ` Sudeep KarkadaNagesha [this message]
2012-10-17 5:39 ` [PATCH 1/2] cpufreq: Improve debug prints Joe Perches
2012-10-17 5:55 ` Viresh Kumar
2012-10-17 6:04 ` Joe Perches
2012-10-17 6:17 ` Viresh Kumar
2012-10-17 6:26 ` Joe Perches
2012-10-17 6:33 ` Viresh Kumar
2012-10-17 6:39 ` Joe Perches
[not found] ` <CAKohpo=fgz98F+1SBG9TgO0EsPd_XLznJ0Z__0ehsgm14EZK7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-24 22:00 ` Rafael J. Wysocki
2012-10-24 22:00 ` Rafael J. Wysocki
2012-10-17 9:25 ` Sudeep KarkadaNagesha
2012-10-17 9:25 ` Sudeep KarkadaNagesha
2012-10-17 9:39 ` Viresh Kumar
2012-10-17 9:58 ` Sudeep KarkadaNagesha
2012-10-17 10:23 ` Viresh Kumar
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=507E787A.3020206@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--cc=PDSW-power-team@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.org \
/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.