From: Kevin Hilman <khilman@deeprootsystems.com>
To: dedekind@infradead.org
Cc: Paul Walmsley <paul@pwsan.com>,
Artem Bityutskiy <dedekind@yandex.ru>,
Tony Lindgen <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3: lessen amount of noisy messages
Date: Fri, 17 Apr 2009 08:41:21 -0500 [thread overview]
Message-ID: <87myaf8kji.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1239810161.3390.190.camel@localhost.localdomain> (Artem Bityutskiy's message of "Wed\, 15 Apr 2009 18\:42\:41 +0300")
Artem Bityutskiy <dedekind@infradead.org> writes:
> Hi,
>
> On Wed, 2009-04-15 at 09:22 -0600, Paul Walmsley wrote:
>> stil thinking about it. These messages have made it easy to catch bugs
>> with the PM code in the past (e.g., sad2d). Making them debug-level will
>> require booting a kernel with clock debugging specifically
>> compiled in. So I wonder if there might be a better way to deal with
>> these...
>
> Yeah, I see your concern. I'm your user, and from my perspective this is
> an excessive output to slow serial line.
>
> If you do not want re-compilation, I may send a different patch
> like this:
>
> - printk(KERN_INFO "Disabling unused clock \"%s\"\n", clk->name);
> + printk(KERN_DEBUG "Disabling unused clock \"%s\"\n", clk->name);
>
> in which case you would not loose the messages, but the messages
> would not go to the serial line.
>
I prefer this method as well since i can see them simply by adding
debug to the cmdline.
Kevin
next prev parent reply other threads:[~2009-04-17 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 14:41 [PATCH] OMAP3: lessen amount of noisy messages Artem Bityutskiy
2009-04-15 12:22 ` Artem Bityutskiy
2009-04-15 13:57 ` Kim Kyuwon
2009-04-15 15:22 ` Paul Walmsley
2009-04-15 15:42 ` Artem Bityutskiy
2009-04-15 16:06 ` Artem Bityutskiy
2009-04-15 18:43 ` Tony Lindgren
2009-04-17 7:34 ` Paul Walmsley
2009-04-17 13:41 ` Kevin Hilman [this message]
2009-04-17 14:26 ` Artem Bityutskiy
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=87myaf8kji.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=dedekind@infradead.org \
--cc=dedekind@yandex.ru \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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