public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <jejb@steeleye.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@suse.de>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH, scsi-block-2.6] ll_rw_blk.c kerneldoc fixups
Date: Tue, 21 Jun 2005 16:41:58 +0200	[thread overview]
Message-ID: <1119364919.5063.3.camel@mulgrave> (raw)
In-Reply-To: <20050620123812.GA6313@lst.de>

On Mon, 2005-06-20 at 14:38 +0200, Christoph Hellwig wrote:
> James, is this the branch you pull into scsi-block-2.6.git?  I try to
> avoid getting lost in all those trees..

Yes, but only the rq-map branch of that repository.

James



      reply	other threads:[~2005-06-21 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-19  9:32 [PATCH, scsi-block-2.6] ll_rw_blk.c kerneldoc fixups Christoph Hellwig
2005-06-20 10:40 ` Jens Axboe
2005-06-20 10:40   ` Christoph Hellwig
2005-06-20 10:53     ` Jens Axboe
2005-06-20 12:24 ` Jens Axboe
2005-06-20 12:38   ` Christoph Hellwig
2005-06-21 14:41     ` James Bottomley [this message]

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=1119364919.5063.3.camel@mulgrave \
    --to=jejb@steeleye.com \
    --cc=axboe@suse.de \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.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