From: Jens Axboe <jens.axboe@oracle.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: William Cohen <wcohen@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add DocBook documentation for the block tracepoints.
Date: Tue, 23 Mar 2010 07:47:04 +0100 [thread overview]
Message-ID: <20100323064704.GR5768@kernel.dk> (raw)
In-Reply-To: <4BA7B45D.2050102@xenotime.net>
On Mon, Mar 22 2010, Randy Dunlap wrote:
> On 03/22/10 11:13, William Cohen wrote:
> > On 03/08/2010 08:18 PM, Randy Dunlap wrote:
> >> On 03/08/10 08:50, William Cohen wrote:
> >>> On 03/06/2010 11:07 PM, Randy Dunlap wrote:
> >>>> William Cohen wrote:
> >>>>> This patch adds a simple description of the various block tracepoints
> >>>>> available in the kernel.
> >>>>>
> >>>>> Signed-off-by: William Cohen <wcohen@redhat.com>
> >>>>
> >>>> Thanks. I have just a few nits below then it will be ready IMO.
> >>>
> >>> I have gone through the patch and made the changes. Below is the updated patch
> >>>
> >>> -Will
> >>>
> >>>
> >>> Signed-off-by: William Cohen <wcohen@redhat.com>
> >>
> >> Thanks, looks good. I'll merge it or get Jens to merge it.
> >
> > Hi Randy,
> >
> > Which git repository is this going into? I didn't see it in any of the git repositories I looked at.
>
> Hi Will,
>
> Jens told me that he would merge it. Jens??
I did, it's in the for-linus branch waiting for a .34 merge.
--
Jens Axboe
next prev parent reply other threads:[~2010-03-23 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1267811199-29812-1-git-send-email-wcohen@redhat.com>
2010-03-07 4:07 ` [PATCH] Add DocBook documentation for the block tracepoints Randy Dunlap
2010-03-08 16:50 ` William Cohen
2010-03-09 1:18 ` Randy Dunlap
2010-03-22 18:13 ` William Cohen
2010-03-22 18:18 ` Randy Dunlap
2010-03-23 6:47 ` Jens Axboe [this message]
2010-03-23 13:59 ` 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=20100323064704.GR5768@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=wcohen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).