From: Mike Christie <michaelc@cs.wisc.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jayamohan Kallickal <jayamohank@serverengines.com>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: linux-next: build failure after merge of the final tree (scsi-post-merge tree related)
Date: Mon, 02 Aug 2010 11:59:47 -0500 [thread overview]
Message-ID: <4C56F983.5080403@cs.wisc.edu> (raw)
In-Reply-To: <20100803024701.b3dff69a.sfr@canb.auug.org.au>
On 08/02/2010 11:47 AM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 3 Aug 2010 02:44:45 +1000 Stephen Rothwell<sfr@canb.auug.org.au> wrote:
>>
>> After merging the final tree, today's linux-next build (powerpc allmodconfig)
>> failed like this:
>>
>> ERROR: ".iscsi_boot_destroy_kset" [drivers/scsi/be2iscsi/be2iscsi.ko] undefined!
>> ERROR: ".iscsi_boot_create_host_kset" [drivers/scsi/be2iscsi/be2iscsi.ko] undefined!
>> ERROR: ".iscsi_boot_create_target" [drivers/scsi/be2iscsi/be2iscsi.ko] undefined!
>> ERROR: ".iscsi_boot_create_initiator" [drivers/scsi/be2iscsi/be2iscsi.ko] undefined!
>> ERROR: ".iscsi_boot_create_ethernet" [drivers/scsi/be2iscsi/be2iscsi.ko] undefined!
>>
>> Caused by commit a33e2a708b2e83ee6111e45c8d3d49a112c3c887 ("[SCSI]
>> be2iscsi: Add support for iscsi boot"). For some reason, commit
>> ed94aa526655d915076dcdbbf4fc962b2a67fcb5 ("[SCSI] be2iscsi: select
>> ISCSI_BOOT_SYSFS") was not sufficient to make sure that
>> CONFIG_ISCSI_BOOT_SYSFS is defined for this build.
>
> It turns out that drivers/firmware/Kconfig is only included on x86, ia64
> and blackfin.
>
I think the iscsi_boot_sysfs module should just be moved to
drivers/scsi. It is a generic scsi/iscsi interface to export iscsi boot
info and is not tied to boot. I will send a patch in a couple minutes.
prev parent reply other threads:[~2010-08-02 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 16:44 linux-next: build failure after merge of the final tree (scsi-post-merge tree related) Stephen Rothwell
2010-08-02 16:47 ` Stephen Rothwell
2010-08-02 16:54 ` James Bottomley
2010-08-02 17:46 ` Mike Christie
2010-08-02 18:59 ` Konrad Rzeszutek Wilk
2010-08-02 19:09 ` Mike Christie
2010-08-02 19:59 ` Konrad Rzeszutek Wilk
2010-08-02 20:14 ` James Bottomley
2010-08-03 0:51 ` Konrad Rzeszutek Wilk
2010-08-05 1:55 ` Stephen Rothwell
2010-08-02 16:59 ` Mike Christie [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=4C56F983.5080403@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jayamohank@serverengines.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.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 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.