From: William Cohen <wcohen@redhat.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Jens Axboe <jens.axboe@oracle.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] add block IO documentation to tracepoint docbook
Date: Wed, 08 Jul 2009 08:46:24 -0400 [thread overview]
Message-ID: <4A549520.3010403@redhat.com> (raw)
In-Reply-To: <4A4C53EE.5000503@cn.fujitsu.com>
Li Zefan wrote:
> More CCed
>
> William Cohen wrote:
>> The following patch adds block IO tracepoint documentation to the tracepoint
>> docbook.
>>
>> Signed-off-by: William Cohen <wcohen@xxxxxxxxxx>
>
> Nice, thanks!
>
> Acked-by: Li Zefan <lizf@cn.fujitsu.com>
>
>> +/**
>> + * block_rq_abort - Abort Block Operation Request
>
> Is it necessary to uppercase the first letter of every word?
I was assuming that it was a title. However, lower case would be okay.
-Will
>
>> + * @q: queue containing the block operation request
>> + * @rq: block IO operation request
>> + *
>> + * Called immediately after pending block IO operation request @rq in
>> + * queue @q is aborted. The fields in the operation request @rq
>> + * can be examined to determine which device and sectors the pending
>> + * operation would access.
>> + */
>> TRACE_EVENT(block_rq_abort,
>>
>> TP_PROTO(struct request_queue *q, struct request *rq),
>
>
next prev parent reply other threads:[~2009-07-08 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 19:53 William Cohen
2009-07-01 22:02 ` Randy Dunlap
2009-07-02 6:30 ` Li Zefan
2009-07-08 12:46 ` William Cohen [this message]
2009-07-02 10:01 ` Christoph Hellwig
2009-07-08 3:13 ` William Cohen
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=4A549520.3010403@redhat.com \
--to=wcohen@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.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
Powered by JetHome