From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined reference to `request_firmware'
Date: Fri, 16 May 2008 13:52:25 -0700 [thread overview]
Message-ID: <20080516135225.e6f8b2c7.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200805162230.41350.rjw@sisk.pl>
On Fri, 16 May 2008 22:30:40 +0200 Rafael J. Wysocki wrote:
> On Friday, 16 of May 2008, Toralf Förster wrote:
> > Hello,
> >
> > the build (.config attached) failed, make ends with :
> > ...
> > UPD include/linux/compile.h
> > CC init/version.o
> > LD init/built-in.o
> > LD vmlinux
> > drivers/built-in.o: In function `sas_request_addr':
> > (.text+0x33bab): undefined reference to `request_firmware'
> > drivers/built-in.o: In function `sas_request_addr':
> > (.text+0x33c3f): undefined reference to `release_firmware'
> > make: *** [vmlinux] Error 1
> >
> > The build was made with :
> > $>make randconfig; make clean; make
>
> Is it the same as http://bugzilla.kernel.org/show_bug.cgi?id=10707 ?
It's in a different driver.
---
~Randy
next prev parent reply other threads:[~2008-05-16 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 17:06 Toralf Förster
2008-05-16 20:30 ` Rafael J. Wysocki
2008-05-16 20:52 ` Randy Dunlap [this message]
2008-05-17 10:04 ` James Bottomley
2008-05-17 14:17 ` Adrian Bunk
2008-05-22 10:52 ` James Bottomley
2008-05-23 17:54 ` Randy Dunlap
2008-05-23 17:59 ` James Bottomley
2008-05-23 18:04 ` Randy Dunlap
2008-05-23 20:33 ` James Bottomley
2008-05-23 21:48 ` Randy Dunlap
2008-05-23 22:00 ` James Bottomley
2008-05-23 22:06 ` Adrian Bunk
2008-05-23 22:39 ` Randy Dunlap
2008-05-23 22:52 ` James Bottomley
2008-06-10 13:24 ` Adrian Bunk
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=20080516135225.e6f8b2c7.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=toralf.foerster@gmx.de \
/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
all inboxes | Powered by JetHome®