[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070726194920K.fujita.tomonori@lab.ntt.co.jp>
Date: Thu, 26 Jul 2007 19:49:20 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: bunk@...sta.de
Cc: apw@...dowen.org, fujita.tomonori@....ntt.co.jp,
michaelc@...wisc.edu, James.Bottomley@...elEye.com,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
drfickle@...ibm.com, mel@....ul.ie, linux-scsi@...r.kernel.org
Subject: Re: 2.6.23-rc1-mm1: SCSI_SRP_ATTRS compile error
From: Adrian Bunk <bunk@...sta.de>
Subject: 2.6.23-rc1-mm1: SCSI_SRP_ATTRS compile error
Date: Wed, 25 Jul 2007 20:06:18 +0200
> On Wed, Jul 25, 2007 at 05:36:56PM +0100, Andy Whitcroft wrote:
> > Of the machines we test releases on automatically this only compiles on
> > NUMA-Q and does not boot there (some PCI issue).
> >
> >
> > ppc64 (beavis):
> >
> > drivers/built-in.o(.text+0xd2784): In function `.srp_rport_add':
> > : undefined reference to `.scsi_tgt_it_nexus_create'
> > drivers/built-in.o(.text+0xd2884): In function `.srp_rport_del':
> > : undefined reference to `.scsi_tgt_it_nexus_destroy'
> > make: *** [.tmp_vmlinux1] Error 1
> >
> >
> > x86_64 (bl6-13):
> >
> > ERROR: "scsi_tgt_it_nexus_destroy" [drivers/scsi/scsi_transport_srp.ko]
> > undefined!
> > ERROR: "scsi_tgt_it_nexus_create" [drivers/scsi/scsi_transport_srp.ko]
> > undefined!
> > make[1]: *** [__modpost] Error 1
> >...
>
> Caused-By : git-scsi-target.patch
> Workaround : enable CONFIG_SCSI_TGT
Sorry about this.
Andrew, could you drop the scsi-target tree from -mm?
I was surprised that the scsi-target tree is still in -mm (it had been
tested in -mm before the mainline inclusion). I guess that it's the
right way to push scsi-target stuff into -mm via James' scsi-misc.
> Is there any good reason why all the SCSI transport attributes options
> are user visible?
No, I messed up the dependency somewhere. I'll fix it before it is
merged into scsi-misc.
Thanks,
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists