From: Steven Rostedt <rostedt@goodmis.org>
To: David Sharp <dhsharp@google.com>
Cc: linux-kernel@vger.kernel.org, mrubin@google.com,
chavey@google.com, Gregory Haskins <gregory.haskins@gmail.com>
Subject: Re: [PATCH] trace-cmd: fix length calculation for padding events
Date: Fri, 27 Jan 2012 14:31:34 -0500 [thread overview]
Message-ID: <1327692694.22710.128.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CAJL_eksfxza82jy62NUPmZGtQ77LVuHk+RnN3F95s-hSaSpK2w@mail.gmail.com>
On Fri, 2012-01-27 at 11:21 -0800, David Sharp wrote:
> > Nice catch! I wonder how long this has been around without notice?
> > Probably from day one.
>
> Yeah, I think so. It's an easy mistake to make, because it's
> incongruent with the rest of the event types.
Yeah, I admit, that was a flaw in the buffer design. :-/
-- Steve
prev parent reply other threads:[~2012-01-27 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 3:00 David Sharp
2012-01-27 3:44 ` Steven Rostedt
2012-01-27 19:21 ` David Sharp
2012-01-27 19:31 ` Steven Rostedt [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=1327692694.22710.128.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=chavey@google.com \
--cc=dhsharp@google.com \
--cc=gregory.haskins@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrubin@google.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
all inboxes | Powered by JetHome®