The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
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: Sat, 17 May 2008 17:17:49 +0300	[thread overview]
Message-ID: <20080517141749.GD3284@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <1211018673.3603.7.camel@localhost.localdomain>

On Sat, May 17, 2008 at 11:04:31AM +0100, James Bottomley wrote:
> On Fri, 2008-05-16 at 19:06 +0200, 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
> 
> There's a slight fault in the stub logic.  It fails for FW_LOADER=m and
> the user =y.
> 
> This should fix it.

An interesting question is whether we actually want to have the stub at 
all - the compile errors catched cases where someone forgot to select 
FW_LOADER at compile time instead of turning them into possible runtime 
problems as will happen after your patch.

Are there any serious use cases where SCSI_SAS_LIBSAS is used in very 
space limited environments and without any other drivers that select 
FW_LOADER in the kernel?

> James
> 
> ---
> 
> diff --git a/include/linux/firmware.h b/include/linux/firmware.h
> index 4d10c73..6c7eff2 100644
> --- a/include/linux/firmware.h
> +++ b/include/linux/firmware.h
> @@ -13,7 +13,7 @@ struct firmware {
>  
>  struct device;
>  
> -#if defined(CONFIG_FW_LOADER) || defined(CONFIG_FW_LOADER_MODULE)
> +#if defined(CONFIG_FW_LOADER) || (defined(CONFIG_FW_LOADER_MODULE) && defined(MODULE))
>  int request_firmware(const struct firmware **fw, const char *name,
>  		     struct device *device);
>  int request_firmware_nowait(

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-05-17 14:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 17:06 build issue #503 for v2.6.26-rc2-433-gf26a398 : undefined reference to `request_firmware' Toralf Förster
2008-05-16 20:30 ` Rafael J. Wysocki
2008-05-16 20:52   ` Randy Dunlap
2008-05-17 10:04 ` James Bottomley
2008-05-17 14:17   ` Adrian Bunk [this message]
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=20080517141749.GD3284@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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