From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 2/2] tracing/fastboot: Use the ring-buffer timestamp for initcall entries
Date: Wed, 12 Nov 2008 11:21:03 +0100 [thread overview]
Message-ID: <20081112102103.GA24482@elte.hu> (raw)
In-Reply-To: <c62985530811120045j5fc0475r8c374f4853f6823e@mail.gmail.com>
* Frédéric Weisbecker <fweisbec@gmail.com> wrote:
> 2008/11/12 Andrew Morton <akpm@linux-foundation.org>:
> > On Wed, 12 Nov 2008 00:54:56 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> >> - unsigned long long duration; /* usecs */
> >> + unsigned long long duration;
> >
> > my hard-won comment got fragged.
>
>
> Oops. I forgot it.
> Perhaps I should resend a patch that reset this comment?
> BTW it is nsecs actually.
no need, i fixed it up when applying your patch to tracing/fastboot,
and also changed it to nsecs.
Ingo
next prev parent reply other threads:[~2008-11-12 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 5:54 [PATCH 0/2] boot tracer updates Steven Rostedt
2008-11-12 5:54 ` [PATCH 1/2] tracing/fastboot: Move boot tracer structs and funcs into their own header Steven Rostedt
2008-11-12 5:54 ` [PATCH 2/2] tracing/fastboot: Use the ring-buffer timestamp for initcall entries Steven Rostedt
2008-11-12 6:00 ` Andrew Morton
2008-11-12 8:45 ` Frédéric Weisbecker
2008-11-12 10:21 ` Ingo Molnar [this message]
2008-11-12 10:33 ` Frédéric Weisbecker
2008-11-12 8:40 ` [PATCH 0/2] boot tracer updates Frédéric Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2008-11-11 22:24 [PATCH 2/2] tracing/fastboot: Use the ring-buffer timestamp for initcall entries Frederic Weisbecker
2008-11-12 9:25 ` Ingo Molnar
2008-11-12 10:58 ` Frédéric Weisbecker
2008-11-12 12:59 ` Steven Rostedt
2008-11-12 13:01 ` 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=20081112102103.GA24482@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.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