From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Steven Rostedt <rostedt@goodmis.org>,
Jens Axboe <jens.axboe@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH tip 1/2] ring_buffer: remove unused flags parameter
Date: Fri, 6 Feb 2009 01:04:55 +0100 [thread overview]
Message-ID: <20090206000455.GE16040@elte.hu> (raw)
In-Reply-To: <20090205221701.GA23999@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > $ codiff /tmp/vmlinux.before /tmp/vmlinux.after
> > linux-2.6-tip/kernel/trace/trace.c:
> > trace_vprintk | -14
> > trace_graph_return | -14
> > trace_graph_entry | -10
> > trace_function | -8
> > __ftrace_trace_stack | -8
> > ftrace_trace_userstack | -8
> > tracing_sched_switch_trace | -8
> > ftrace_trace_special | -12
> > tracing_sched_wakeup_trace | -8
> > 9 functions changed, 90 bytes removed, diff: -90
> >
> > linux-2.6-tip/block/blktrace.c:
> > __blk_add_trace | -1
> > 1 function changed, 1 bytes removed, diff: -1
> >
> > /tmp/vmlinux.after:
> > 10 functions changed, 91 bytes removed, diff: -91
>
>
> codiff... I didn't know this great tool! :-)
yes, very nice!
I've moved all the codiff output from the (discarded) diffstat
section into the commit log, they are very much worth preserving.
Ingo
next prev parent reply other threads:[~2009-02-06 0:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 18:12 [PATCH tip 1/2] ring_buffer: remove unused flags parameter Arnaldo Carvalho de Melo
2009-02-05 22:17 ` Frederic Weisbecker
2009-02-05 22:39 ` Steven Rostedt
2009-02-05 23:27 ` Frederic Weisbecker
2009-02-06 0:04 ` Ingo Molnar [this message]
2009-02-06 0:06 ` Ingo Molnar
2009-02-06 0:09 ` Frederic Weisbecker
2009-02-06 1:48 ` Arnaldo Carvalho de Melo
2009-02-06 2:41 ` Frederic Weisbecker
2009-02-06 0:02 ` Ingo Molnar
2009-02-06 0:15 ` [PATCH] ring_buffer: remove unused flags parameter, fix Ingo Molnar
2009-02-06 1:43 ` Arnaldo Carvalho de Melo
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=20090206000455.GE16040@elte.hu \
--to=mingo@elte.hu \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox