From: Jens Axboe <jens.axboe@oracle.com>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
bhalevy@panasas.com, Andrew Morton <akpm@linux-foundation.org>,
fujita.tomonori@lab.ntt.co.jp, michaelc@cs.wisc.edu
Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
Date: Tue, 15 May 2007 19:50:26 +0200 [thread overview]
Message-ID: <20070515175025.GE23798@kernel.dk> (raw)
In-Reply-To: <1179251020.2836.118.camel@dyn9047017100.beaverton.ibm.com>
On Tue, May 15 2007, Badari Pulavarty wrote:
> On Tue, 2007-05-15 at 19:20 +0200, Jens Axboe wrote:
> > On Tue, May 15 2007, Badari Pulavarty wrote:
> > > On Fri, 2007-05-11 at 15:51 +0200, Jens Axboe wrote:
> > > > Hi,
> > > >
> > > > Updated version of the patch - this time I'll just attach the patch
> > > > file...
> > >
> > > Missing scatterlist.h inclusions..
> > >
> > > drivers/scsi/sym53c8xx_2/sym_glue.c: In function ???sym_scatter???:
> > > drivers/scsi/sym53c8xx_2/sym_glue.c:385: warning: implicit declaration
> > > of function ???for_each_sg???
> > > drivers/scsi/sym53c8xx_2/sym_glue.c:385: error: expected ???;??? before ???{???
> > > token
> > > drivers/scsi/sym53c8xx_2/sym_glue.c:375: warning: unused variable ???tp???
> > > make[3]: *** [drivers/scsi/sym53c8xx_2/sym_glue.o] Error 1
> > >
> > >
> > > drivers/scsi/qla2xxx/qla_iocb.c: In function ???qla24xx_build_scsi_iocbs???:
> > > drivers/scsi/qla2xxx/qla_iocb.c:678: warning: implicit declaration of
> > > function ???for_each_sg???
> > > drivers/scsi/qla2xxx/qla_iocb.c:678: error: expected ???;??? before ???{???
> > > token
> >
> > Thanks, will fix those. What arch? I tested it here.
>
> I am playing with them on ppc64.
Ah ok, you need the updated patch series for ppc64 support. Builds fine
here on ppc64. See the #sglist branch of the block repo:
git://git.kernel.dk/data/git/linux-2.6-block.git
I can mail you an updated patch, if you want.
--
Jens Axboe
next prev parent reply other threads:[~2007-05-15 17:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 13:51 [PATCH] Chaining sg lists for big IO commands v5 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 [this message]
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
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=20070515175025.GE23798@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.