From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-scsi <linux-scsi@vger.kernel.org>,
"Darrick J. Wong" <djwong@us.ibm.com>
Subject: [Fwd: next-2008-0306 scsi/libsas build failure]
Date: Thu, 06 Mar 2008 11:09:18 -0600 [thread overview]
Message-ID: <1204823359.3062.21.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Forwarded message - next-2008-0306 scsi/libsas build failure --]
[-- Type: message/rfc822, Size: 2587 bytes --]
From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-next@vger.kenrel.org
Cc: jejb <James.Bottomley@HansenPartnership.com>
Subject: next-2008-0306 scsi/libsas build failure
Date: Thu, 6 Mar 2008 09:05:33 -0800
Message-ID: <20080306090533.bdc3783a.randy.dunlap@oracle.com>
drivers/built-in.o: In function `sas_request_addr':
(.text+0x598fb): undefined reference to `request_firmware'
drivers/built-in.o: In function `sas_request_addr':
(.text+0x5998e): undefined reference to `release_firmware'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2
drivers/scsi/libsas/sas_scsi_host.c calls request_firmware() and
release_firmware() without checking to see if CONFIG_FW_LOADER=y.
---
~Randy
reply other threads:[~2008-03-06 17:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1204823359.3062.21.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=djwong@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
/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