From: Arjan van de Ven <arjan@infradead.org>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: mingo@elte.hu, rostedt@goodmis.org, linux-kernel@vger.kernel.org,
alan-jenkins@tuffmail.co.uk
Subject: Re: [PATCH -tip] Fastboot: fix initcalls disposition in bootgraph.pl
Date: Sat, 4 Oct 2008 13:39:40 -0700 [thread overview]
Message-ID: <20081004133940.44feb2a0@infradead.org> (raw)
In-Reply-To: <c62985530810041328i282818cak8cd0ba36c450e3d6@mail.gmail.com>
On Sat, 4 Oct 2008 22:28:49 +0200
"Frédéric Weisbecker" <fweisbec@gmail.com> wrote:
> I'm tracing all of the initcalls in my machine (even the modules).
> If you look at both svg sources, you will see all of the 5 initcalls
> displayed. But for the "before the patch" one, it depends on the
> software you are using to visualize it.
> With firefox you only see two of them. With the default gnome
> visualization software (don't remember its name)
> you can see all of them but in a very extensive image because a lot of
> rows are unused.
>
> With the "after the patch one", there is no issues....
fair enough
Acked-by: Arjan van de Ven <arjan@linux.intel.com>
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-10-04 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 19:35 [PATCH -tip] Fastboot: fix initcalls disposition in bootgraph.pl Frederic Weisbecker
2008-10-04 20:19 ` Arjan van de Ven
2008-10-04 20:28 ` Frédéric Weisbecker
2008-10-04 20:39 ` Arjan van de Ven [this message]
2008-10-05 9:55 ` Ingo Molnar
2008-10-05 11:22 ` Frédéric Weisbecker
[not found] ` <20081006071209.GB23506@elte.hu>
[not found] ` <c62985530810060213k189095e5xb791e98db45c370d@mail.gmail.com>
2008-10-06 12:20 ` Frederic Weisbecker
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=20081004133940.44feb2a0@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