From: James Bottomley <James.Bottomley@SteelEye.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: jens.axboe@oracle.com, pbadari@gmail.com,
linux-kernel@vger.kernel.org, bhalevy@panasas.com,
akpm@linux-foundation.org, michaelc@cs.wisc.edu
Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
Date: Thu, 24 May 2007 11:08:56 -0500 [thread overview]
Message-ID: <1180022937.3692.34.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070525010134I.fujita.tomonori@lab.ntt.co.jp>
On Fri, 2007-05-25 at 01:01 +0900, FUJITA Tomonori wrote:
> From: James Bottomley <James.Bottomley@SteelEye.com>
> Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
> Date: Thu, 24 May 2007 10:39:44 -0500
>
> > On Thu, 2007-05-24 at 21:44 +0900, FUJITA Tomonori wrote:
> > > (cc's added)
> > >
> > > From: Jens Axboe <jens.axboe@oracle.com>
> > > Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
> > > Date: Thu, 24 May 2007 14:05:54 +0200
> > >
> > > > On Thu, May 24 2007, Jens Axboe wrote:
> > > > > > http://git.kernel.org/?p=linux/kernel/git/tomo/linux-2.6-bidi.git;a=commitdiff;h=fb2747a9f2465ac4a1ea9e3533b92510fbcaae0c
> > > > >
> > > > > Neat, will take a look! I should be able to just reuse that.
> > > >
> > > > BTW, when do you plan on pushing the SCSI sg update? I'd love for it to
> > > > be soon, so I can just rebase the sglist branch on that and get rid of
> > > > the SCSI stuff in there.
> > >
> > > Well, all I can say is that I'd love James to push the cleanups
> > > patchset soon too.
> >
> > I'll put the accessor one into scsi-misc. I'll try to get the other 40
> > reviewed via the scsi-pending tree that Mark Salyzyn suggested ... give
> > me some time on that.
>
> Thanks. Do you want me to send the patches to scsi-ml or you directly
> get them via the git tree?
Either works ... but for 40 patches it was easier for me to fetch into a
git branch and cherry pick the two that can go into scsi-misc now.
I'm just correcting a compile warning on the 53c700 one, then I'll push.
James
next prev parent reply other threads:[~2007-05-24 16:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 13:51 Jens Axboe
2007-05-15 17:15 ` Badari Pulavarty
2007-05-15 17:20 ` Jens Axboe
2007-05-15 17:43 ` Badari Pulavarty
2007-05-15 17:50 ` Jens Axboe
2007-05-15 18:23 ` Jens Axboe
2007-05-16 20:58 ` Badari Pulavarty
2007-05-16 21:01 ` Badari Pulavarty
2007-05-17 6:27 ` Jens Axboe
2007-05-17 15:11 ` Badari Pulavarty
2007-05-18 7:33 ` Jens Axboe
2007-05-18 16:03 ` Badari Pulavarty
2007-05-18 17:03 ` Jens Axboe
2007-05-18 17:50 ` Badari Pulavarty
2007-05-17 15:15 ` Badari Pulavarty
2007-05-18 7:35 ` Jens Axboe
2007-05-18 17:51 ` Badari Pulavarty
2007-05-21 6:14 ` Jens Axboe
2007-05-21 6:35 ` Jens Axboe
2007-05-21 7:14 ` Benny Halevy
2007-05-22 22:15 ` Badari Pulavarty
2007-05-24 9:34 ` Jens Axboe
2007-05-24 9:43 ` FUJITA Tomonori
2007-05-24 10:00 ` Jens Axboe
2007-05-24 12:05 ` Jens Axboe
2007-05-24 12:44 ` FUJITA Tomonori
2007-05-24 12:49 ` Jens Axboe
2007-05-24 15:39 ` James Bottomley
2007-05-24 16:01 ` FUJITA Tomonori
2007-05-24 16:08 ` James Bottomley [this message]
2007-05-24 12:05 ` Jens Axboe
2007-05-24 15:25 ` Badari Pulavarty
2007-05-25 6:49 ` Jens Axboe
2007-05-22 15:35 ` Badari Pulavarty
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=1180022937.3692.34.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=pbadari@gmail.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
all inboxes | Powered by JetHome®