From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH 0/3] git pull request for tip/tracing/ftrace
Date: Tue, 10 Feb 2009 14:00:50 +0100 [thread overview]
Message-ID: <20090210130050.GA8341@elte.hu> (raw)
In-Reply-To: <20090209172830.087244662@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> Ingo,
>
> I pulled in the splice code from Eduard into a branch that is
> based off of tip's tracing/ftrace branch.
>
> I kept Eduard's patches as is, and implemented the suggested clean
> ups at the end.
>
> My branch names were getting too long so I hacked off the "/devel"
> part at the end that I usually have.
> Eduard - Gabriel Munteanu (2):
> tracing: splice support for tracing_pipe
> tracing: Move pipe waiting code out of tracing_read_pipe().
>
> Steven Rostedt (1):
> tracing: clean up splice code
>
> ----
> kernel/trace/trace.c | 219 +++++++++++++++++++++++++++++++++++++++++++-------
> kernel/trace/trace.h | 6 ++
> 2 files changed, 196 insertions(+), 29 deletions(-)
Pulled into tip:tracing/ftrace, thanks guys!
A small request regarding the commit logs, could you please
in the future make the titles more consistent:
34cd499: tracing: clean up splice code
ff98781: tracing: Move pipe waiting code out of tracing_read_pipe().
3c56819: tracing: splice support for tracing_pipe
the closing period in the second commit is unnecessary, and
capitalization should be consistent as well.
Thanks,
Ingo
next prev parent reply other threads:[~2009-02-10 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 17:28 [PATCH 0/3] git pull request for tip/tracing/ftrace Steven Rostedt
2009-02-09 17:28 ` [PATCH 1/3] tracing: splice support for tracing_pipe Steven Rostedt
2009-02-09 17:28 ` [PATCH 2/3] tracing: Move pipe waiting code out of tracing_read_pipe() Steven Rostedt
2009-02-09 17:33 ` Frederic Weisbecker
2009-02-09 17:28 ` [PATCH 3/3] tracing: clean up splice code Steven Rostedt
2009-02-09 18:25 ` Eduard - Gabriel Munteanu
2009-02-09 18:26 ` Pekka Enberg
2009-02-09 18:37 ` Eduard - Gabriel Munteanu
2009-02-09 18:43 ` Steven Rostedt
2009-02-10 13:00 ` Ingo Molnar [this message]
2009-02-10 14:08 ` [PATCH 0/3] git pull request for tip/tracing/ftrace Steven Rostedt
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=20090210130050.GA8341@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--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 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.