From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jens Axboe <jens.axboe@oracle.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 2/2] blktrace: fix output of BLK_TC_PC events
Date: Mon, 13 Apr 2009 08:43:00 +0800 [thread overview]
Message-ID: <49E28A94.1050700@cn.fujitsu.com> (raw)
In-Reply-To: <20090412133714.GB384@elte.hu>
Ingo Molnar wrote:
> * Jens Axboe <jens.axboe@oracle.com> wrote:
>
>> On Sun, Apr 12 2009, Ingo Molnar wrote:
>>> * Li Zefan <lizf@cn.fujitsu.com> wrote:
>>>
>>>> Hi Ingo,
>>>>
>>>> I would like to ask what's the status of these 2 patches.
>>>>
>>>> Arnaldo acked on them.
>>> They looked good to me - but i'm waiting for an Ack from Jens. Jens
>>> has complained about seeing un-ack-ed patches in the blktrace code,
>>> so i've started serializing any new patches on acks from Jens. The
>>> workflow would be more efficient i suspect if Jens
>>> nominated/declared you and Arnaldo as blktrace co-maintainers too -
>>> most of the patches come from you two.
>> I'd be fine with listing Li Zefan as co-maintainer of the blktrace
>> bits. He knows what he is doing and is also a user of blktrace, so
>> I think he would be fine. Li, what do you think?
>
> Cool ... i've also taken this as an implicit approval from you of Li
> sending blktrace patches so i have queued the two up.
>
Thanks!
> The next big (and nice!) step would be the blktrace events in
> TRACE_EVENT() style. That would integrate the blktrace tracepoints
> with all the others, in one coherent framework.
>
As I mentioned in another mail thread, this is what we are planning
to do. :)
--
Zefan
next prev parent reply other threads:[~2009-04-13 0:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 8:18 [PATCH 1/2] blktrace: fix output of unknown events Li Zefan
2009-04-01 8:19 ` [PATCH 2/2] blktrace: fix output of BLK_TC_PC events Li Zefan
2009-04-01 11:00 ` Ingo Molnar
2009-04-01 12:52 ` Arnaldo Carvalho de Melo
2009-04-11 8:15 ` Li Zefan
2009-04-12 13:07 ` Ingo Molnar
2009-04-12 13:10 ` Jens Axboe
2009-04-12 13:37 ` Ingo Molnar
2009-04-13 0:43 ` Li Zefan [this message]
2009-04-13 0:40 ` Li Zefan
2009-04-13 22:22 ` [tip:tracing/core] " tip-bot for Li Zefan
2009-04-01 12:46 ` [PATCH 1/2] blktrace: fix output of unknown events Arnaldo Carvalho de Melo
2009-04-13 22:22 ` [tip:tracing/core] " tip-bot for Li Zefan
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=49E28A94.1050700@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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