[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpo=i+LAFR1JWen0n3c1-3vHOm52G5bt7ty-4q2QKpuQRXA@mail.gmail.com>
Date: Wed, 17 Oct 2012 15:53:38 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@....com>
Cc: "rjw@...k.pl" <rjw@...k.pl>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linaro-dev@...ts.linaro.org" <linaro-dev@...ts.linaro.org>,
"patches@...aro.org" <patches@...aro.org>,
PDSW-power-team <PDSW-power-team@....com>
Subject: Re: [PATCH 1/2] cpufreq: Improve debug prints
On 17 October 2012 15:28, Sudeep KarkadaNagesha
<Sudeep.KarkadaNagesha@....com> wrote:
> May be kernel/Documentation/dynamic-debug-howto.txt is more up-to-date.
yes.
>> My usecase is a bit different. I want to see all bootprints with
>> cpufreq pr_debug
>> prints. So, this prefixing will help there.
> The document covers "Debug messages during Boot Process" even though I have
> never tried :)
Looks like it does. That's good.
But this patch is anyway required, because of the earlier mentioned reason.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists