linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	scsi <linux-scsi@vger.kernel.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Robert Love <robert.w.love@intel.com>
Subject: Re: linux-next: Tree for December 29 (fcoe/libfc)
Date: Tue, 30 Dec 2008 09:44:29 -0600	[thread overview]
Message-ID: <1230651870.3296.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20081229195358.6a239657.randy.dunlap@oracle.com>

On Mon, 2008-12-29 at 19:53 -0800, Randy Dunlap wrote:
> On Tue, 30 Dec 2008 03:16:21 +1100 Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > Changes since 20081219:
> > 
> > Undropped tree:
> > 	scci
> > 	mtd
> > 
> > Dropped trees (temporarily):
> > 	nfs (akpm request due to 2.6.30 features)
> > 	kvm (build problem)
> > 	rr (build poblem)
> > 	semaphore-removal (due to unfixed conflicts against Linus' tree)
> > 	cpu_alloc (build problem)
> > 	audit (difficult conflicts)
> > 
> > Linus' tree had three build failures requiring patches and one requiring
> > a revert.
> 
> 
> >From drivers/scsi/Kconfig:
> 
> config LIBFC
> 	tristate "LibFC module"
> 	depends on SCSI && SCSI_FC_ATTRS
> 	---help---
> 	  Fibre Channel library module
> 
> config FCOE
> 	tristate "FCoE module"
> 	depends on SCSI
> 	select LIBFC
> 	---help---
> 	  Fibre Channel over Ethernet module
> 
> 
> Aside from being very skimpy help messages, nothing there requires
> SCSI_FC_ATTRS to be enabled for FCOE, so when FCOE is enabled,
> LIBFC is selected, and then bang:
> 
> ERROR: "scsi_is_fc_rport" [drivers/scsi/libfc/libfc.ko] undefined!
> ERROR: "fc_remote_port_delete" [drivers/scsi/libfc/libfc.ko] undefined!
> ERROR: "fc_remote_port_add" [drivers/scsi/libfc/libfc.ko] undefined!
> ERROR: "fc_release_transport" [drivers/scsi/fcoe/fcoe.ko] undefined!
> ERROR: "fc_remove_host" [drivers/scsi/fcoe/fcoe.ko] undefined!
> ERROR: "fc_attach_transport" [drivers/scsi/fcoe/fcoe.ko] undefined!

I checked the select of an option that selects, it seems to work nicely,
so I think this is the fix.  The custom has been to select the
attributes rather than depend on them anyway.  There's also no need to
depend on SCSI since the whole thing is enclosed in an if SCSI_LOWLEVEL
&& SCSI.

James

---


diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index 0e5e084..9f4cc8e 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -607,13 +607,12 @@ config SCSI_FLASHPOINT
 
 config LIBFC
 	tristate "LibFC module"
-	depends on SCSI && SCSI_FC_ATTRS
+	select SCSI_FC_ATTRS
 	---help---
 	  Fibre Channel library module
 
 config FCOE
 	tristate "FCoE module"
-	depends on SCSI
 	select LIBFC
 	---help---
 	  Fibre Channel over Ethernet module



  reply	other threads:[~2008-12-30 15:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 16:16 linux-next: Tree for December 29 Stephen Rothwell
2008-12-29 20:31 ` linux-next: Tree for December 29 (fcoe) Randy Dunlap
2008-12-29 21:35   ` James Bottomley
2008-12-29 21:45     ` James Bottomley
2008-12-29 22:21       ` Randy Dunlap
2008-12-29 20:35 ` linux-next: Tree for December 29 (cxgb3i) Randy Dunlap
2008-12-29 21:51   ` James Bottomley
2008-12-29 22:10     ` Randy Dunlap
2008-12-29 21:01 ` [PATCH -next] cxgb3i: use same dependencies as CHELSIO_T3 Randy Dunlap
2008-12-29 21:23   ` [PATCH -next v2] cxgb3i: use same dependencies & selects " Randy Dunlap
2008-12-29 21:58     ` James Bottomley
2008-12-29 22:08       ` Randy Dunlap
2008-12-30 16:20         ` James Bottomley
2008-12-30  3:53 ` linux-next: Tree for December 29 (fcoe/libfc) Randy Dunlap
2008-12-30 15:44   ` James Bottomley [this message]
2008-12-30 16:54     ` Randy Dunlap
2008-12-30 17:12       ` James Bottomley
2008-12-30 17:36         ` Randy Dunlap
2008-12-30 17:40         ` Kamalesh Babulal
2008-12-30 15:45 ` [BUILD-FAILURE] fcoe driver build fails with !CONFIG_PCI Kamalesh Babulal

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=1230651870.3296.2.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=robert.w.love@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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).