From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] blktrace: last round of fixes
Date: Sun, 29 Mar 2009 20:02:36 +0200 [thread overview]
Message-ID: <20090329180235.GC5178@kernel.dk> (raw)
In-Reply-To: <20090328224640.GA2465@elte.hu>
On Sat, Mar 28 2009, Ingo Molnar wrote:
>
> * Li Zefan <lizf@cn.fujitsu.com> wrote:
>
> > This is the last round of fixes for blktrace, I hope. :)
> >
> > Changelog v1 -> v2:
> > - fix a bug in "blktrace: make classic output more classic",
> > and rebase other patches.
> > - re-order patches.
> > - a new patch for filtering BLK_TN_MESSAGE
> >
> > [PATCH v2 1/6] trace: make 'mem' argument of trace_seq_putmem() const
> > [PATCH v2 2/6] blktrace: make classic output more classic
> > [PATCH v2 3/6] blktrace: fix blk_probes_ref chaos
> > [PATCH v2 4/6] blktrace: fix memory leak when freeing struct blk_io_trace
> > [PATCH v2 5/6] blktrace: extract duplidate code
> > [PATCH v2 6/6] blktrace: print out BLK_TN_MESSAGE properly
> > ---
> > blktrace.c | 188 +++++++++++++++++++++++++++++++++------------------------
> > trace_output.c | 6 -
> > trace_output.h | 5 -
> > 3 files changed, 117 insertions(+), 82 deletions(-)
>
> Li, Jens - what's your call for v2.6.30, can the blktrace changes go
> upstream or should i zap the whole thing?
>
> There are no new -tip test failures here so it's green as far as i'm
> concerned. It's holding up the tracing tree so we need to decide one
> way or another.
If Li deems it ready, then it has my blessing as well.
--
Jens Axboe
next prev parent reply other threads:[~2009-03-29 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 5:39 [PATCH v2 0/7] blktrace: last round of fixes Li Zefan
2009-03-27 5:39 ` [PATCH v2 1/7] trace: make 'mem' argument of trace_seq_putmem() const Li Zefan
2009-03-27 5:40 ` [PATCH v2 2/7] blktrace: make classic output more classic Li Zefan
2009-03-27 5:40 ` [PATCH v2 3/7] blktrace: fix blk_probes_ref chaos Li Zefan
2009-03-27 8:13 ` [PATCH v3 " Li Zefan
2009-03-27 5:40 ` [PATCH v2 4/7] blktrace: fix memory leak when freeing struct blk_io_trace Li Zefan
2009-03-27 8:13 ` [PATCH v3 " Li Zefan
2009-03-27 5:41 ` [PATCH v2 5/7] blktrace: extract duplidate code Li Zefan
2009-03-27 5:41 ` [PATCH v2 6/7] blktrace: print out BLK_TN_MESSAGE properly Li Zefan
2009-03-27 5:42 ` [PATCH v2 7/7] blktrace: support filtering of BLK_TN_MESSAGE Li Zefan
2009-03-27 9:42 ` [PATCH v2 0/7] blktrace: last round of fixes Ingo Molnar
2009-03-28 22:46 ` Ingo Molnar
2009-03-29 18:02 ` Jens Axboe [this message]
2009-03-30 1:17 ` Ingo Molnar
2009-03-30 0:40 ` Li Zefan
2009-03-30 1:23 ` 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=20090329180235.GC5178@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--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