From: Frederic Weisbecker <fweisbec@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Paul Mackerras <paulus@samba.org>, Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH] perf timechart: Use pr_debug to report unknown header types
Date: Fri, 23 Oct 2009 20:56:08 +0200 [thread overview]
Message-ID: <20091023185605.GA4913@nowhere> (raw)
In-Reply-To: <4AE1F807.9060907@linux.intel.com>
On Fri, Oct 23, 2009 at 11:37:59AM -0700, Arjan van de Ven wrote:
> Arnaldo Carvalho de Melo wrote:
>> Em Fri, Oct 23, 2009 at 10:55:39AM -0700, Arjan van de Ven escreveu:
>>> Arnaldo Carvalho de Melo wrote:
>>>> It was using eprintf that checked if verbose was !zero, when I converted
>>>> to pr_*() I made the mistake of changing it to pr_warning which caused
>>>> 'perf timechart' output to be way too verbose.
>>>>
>>> nack...
>>>
>>> if you EVER hit one of these you have a very very serious problem.
>>> hiding that is never the right thing to do. I should make this a fatal
>>> event instead.
>>
>> OK, so I actually fixed a bug as those messages weren't being noticed if
>> -v wasn't used! :-)
>>
>> Please take a look at latest tip to see all those messages.
>>
>> - Arnaldo
>
> I'm pretty sure latest -tip broke timechart; Frederic tends to have a habit of doing so occasionally :)
>
Yeah but I usually fix what I break. Because I need the things to be working
again if I want to happily continue breaking them :o)
/me wonders if he hasn't played too much legos when he was a child. That
may have provided him a strange vision of the world.
That said I've tested timechart few days ago and it worked very well. (That
was also the first time it worked for me).
So I guess it should be fine.
prev parent reply other threads:[~2009-10-23 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 17:50 [PATCH] perf timechart: Use pr_debug to report unknown header types Arnaldo Carvalho de Melo
2009-10-23 17:55 ` Arjan van de Ven
2009-10-23 18:31 ` Arnaldo Carvalho de Melo
2009-10-23 18:37 ` Arjan van de Ven
2009-10-23 18:56 ` Frederic Weisbecker [this message]
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=20091023185605.GA4913@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@infradead.org \
--cc=arjan@linux.intel.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.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.