From: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, yrl.pp-manager.tt@hitachi.com,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH -tip 2/4] tracing: add a resize function for making one buffer equivalent to the other buffer
Date: Wed, 17 Oct 2012 11:47:37 +0900 [thread overview]
Message-ID: <507E1C49.1030002@hitachi.com> (raw)
In-Reply-To: <1349456348.6755.59.camel@gandalf.local.home>
Steven,
I'm sorry for my late reply.
(I was outside the office for business trip.)
(2012/10/06 1:59), Steven Rostedt wrote:
>> +/* resize @tr's buffer to the size of @size_tr's entries */
>> +static int resize_buffer_even(struct trace_array *tr,
>
> I don't mind this patch, but I just hate the name "resize_buffer_even".
> What about "resize_buffer_duplicate_size"?
>
O.K.
I'll send modified version of this patch later.
Regards,
Hiraku Toyooka
next prev parent reply other threads:[~2012-10-17 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 8:13 [PATCH -tip 0/4] tracing: make a snapshot feature available from userspace Hiraku Toyooka
2012-10-02 8:27 ` [PATCH -tip 1/4] tracing: change tracer's integer flags to bool Hiraku Toyooka
2012-11-14 6:43 ` [tip:perf/core] tracing: Change " tip-bot for Hiraku Toyooka
2012-10-02 8:27 ` [PATCH -tip 2/4] tracing: add a resize function for making one buffer equivalent to the other buffer Hiraku Toyooka
2012-10-05 16:59 ` Steven Rostedt
2012-10-17 2:47 ` Hiraku Toyooka [this message]
2012-10-17 2:57 ` Steven Rostedt
2012-10-02 8:27 ` [PATCH -tip 3/4] tracing: make a snapshot feature available from userspace Hiraku Toyooka
2012-10-02 8:27 ` [PATCH -tip 4/4] tracing: add description of snapshot to Documentation/trace/ftrace.txt Hiraku Toyooka
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=507E1C49.1030002@hitachi.com \
--to=hiraku.toyooka.gu@hitachi.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yrl.pp-manager.tt@hitachi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.