From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
"Alan Jenkins" <alan-jenkins@tuffmail.co.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>
Subject: Re: Re : [PATCH 2/2] fastboot: fix row order in bootgraph.pl
Date: Wed, 22 Oct 2008 10:56:49 -0700 [thread overview]
Message-ID: <20081022105649.7dbb288b@infradead.org> (raw)
In-Reply-To: <20081022143741.GA3263@elte.hu>
On Wed, 22 Oct 2008 16:37:41 +0200
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Frédéric Weisbecker <fweisbec@gmail.com> wrote:
>
> > 2008/10/14, Alan Jenkins <alan-jenkins@tuffmail.co.uk>:
> > > When bootgraph.pl parses a file, it gives one row for each
> > > initcall's pid. But they are displayed in random (perl hash)
> > > order. Let's sort the pids by the start time of their first
> > > initcall instead.
> >
> > Thanks. That's a good idea!
> >
> > I can't test it yet but I will give you a feedback as soon as I can.
>
> i've applied the two fix patches from Alan to tip/tracing/urgent:
>
> 06d1cd2: tracing/fastboot: fix row order in bootgraph.pl
> 2a813f8: tracing/fastboot: fix bootgraph.pl to run with "use strict"
>
> Arjan, Steve, any objections?
>
> Ingo
fine with me
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
prev parent reply other threads:[~2008-10-22 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 13:18 [PATCH 1/2] fastboot: fix bootgraph.pl to run with "use strict" Alan Jenkins
2008-10-14 13:19 ` [PATCH 2/2] fastboot: fix row order in bootgraph.pl Alan Jenkins
2008-10-14 14:01 ` Re : " Frédéric Weisbecker
2008-10-22 14:37 ` Ingo Molnar
2008-10-22 17:48 ` Steven Rostedt
2008-10-22 17:56 ` Arjan van de Ven [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=20081022105649.7dbb288b@infradead.org \
--to=arjan@infradead.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox