mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Steven Noonan" <steven@uplinklabs.net>,
	"Arjan van de Ven" <arjan@infradead.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: [Patch -tip 0/4] Creation of the initcall tracer
Date: Tue, 23 Sep 2008 13:42:18 +0200	[thread overview]
Message-ID: <c62985530809230442w217642a7o7742c51da905083d@mail.gmail.com> (raw)
In-Reply-To: <20080923100034.GA23118@elte.hu>

2008/9/23 Ingo Molnar <mingo@elte.hu>:
> Note that i've done a couple of small changes to your patches:
>
>  - i've done the following renames:
>
>      :1,$s/INITCALL_TRACER/BOOT_TRACER/g
>      :1,$s/trace_initcall/trace_boot/g
>      :1,$s/initcall_trace/boot_trace/g
>
>   the reasoning: we eventually want to extend this new tracer to all
>   things "bootup delay", not just initcalls - hence calling it an
>   'initcall tracer' would be too limiting.

That's right. It's a good thing.

>
>   The goal is to help the Arjan's fastboot project to achieve 5 seconds
>   to-GUI bootup times like this:
>
>      http://www.youtube.com/watch?v=s7NxCM8ryF8
>
>   [ Even if you know what a 5 seconds bootup is, you've got to check
>     this "From Naught to Sixty in 5 seconds" video ;-) ]

Hehe! I wasn't aware of this project :)

>  - there were a few overlong lines in the commit logs and in the Kconfig
>   desciption - i fixed them up. You should check your email client and
>   your editor for line length settings - currently you seem to have no
>   line breaks at all.

That will be a great day when I will be able to send a not line/space
damaged patch :-)

>  - I also corrected a few capitalization things in commit subject lines
>   and corrected a few minor coding style errors - you can avoid these
>   by running scripts/checkpatch.pl over your patches. Nothing overly
>   serious - but you should diff against tip/master to see what the
>   changes are.

Hmm I ran this script and it warned about a non conventional format
(%Lu instead of %llu). Since I picked it from the printk in main.c
I thought that was a false warning. Ok I will remember about correct
format for the next times.

> i've integrated tip/tracing/fastboot into tip/master and have started
> testing it. It passed the basic tests already so i've just pushed out
> the new tip/master. Please double-check that i have not messed up the
> rename or the integration somewhere.

I can't test the master branch yet. But as far as I read the diff, it
seems correct.

> all in one, nice stuff!

Thanks Ingo :)
I will improve it as I can...

  reply	other threads:[~2008-09-23 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 10:29 Frédéric Weisbecker
2008-09-23 10:00 ` Ingo Molnar
2008-09-23 11:42   ` Frédéric Weisbecker [this message]
2008-09-23 19:31   ` Ingo Molnar
2008-09-24  9:36     ` Frédéric Weisbecker
2008-09-24  8:58       ` Ingo Molnar

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=c62985530809230442w217642a7o7742c51da905083d@mail.gmail.com \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=steven@uplinklabs.net \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®