archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <>
To: Stephen Rothwell <>
	"" <>
Subject: Re: linux-next: Tree for Apr 29 (staging/gdm72xx)
Date: Mon, 29 Apr 2013 09:42:12 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 04/29/13 02:17, Stephen Rothwell wrote:
> Hi all,
> Changes since 20130426:

on x86_64:

when CONFIG_MMC=m and
CONFIG_WIMAX_GDM72XX_SDIO=y (because it is boolean, not tristate):

gdm_sdio.c:(.text+0x147093): undefined reference to `sdio_claim_host'
gdm_sdio.c:(.text+0x1470a2): undefined reference to `sdio_release_irq'
gdm_sdio.c:(.text+0x1470b1): undefined reference to `sdio_disable_func'
gdm_sdio.c:(.text+0x1470c0): undefined reference to `sdio_release_host'
gdm_sdio.c:(.text+0x14725a): undefined reference to `sdio_claim_host'
gdm_sdio.c:(.text+0x14728f): undefined reference to `sdio_memcpy_toio'
gdm_sdio.c:(.text+0x1472fa): undefined reference to `sdio_memcpy_toio'
gdm_sdio.c:(.text+0x147342): undefined reference to `sdio_release_host'
gdm_sdio.c:(.text+0x1477b6): undefined reference to `sdio_readb'
gdm_sdio.c:(.text+0x1477db): undefined reference to `sdio_writeb'
gdm_sdio.c:(.text+0x1477f5): undefined reference to `sdio_memcpy_fromio'
gdm_sdio.c:(.text+0x14795b): undefined reference to `sdio_memcpy_fromio'
gdm_sdio.c:(.text+0x1479ba): undefined reference to `sdio_memcpy_fromio'
gdm_sdio.c:(.text+0x147ba8): undefined reference to `sdio_writeb'
gdm_sdio.c:(.text+0x147f45): undefined reference to `sdio_claim_host'
gdm_sdio.c:(.text+0x147f54): undefined reference to `sdio_enable_func'
gdm_sdio.c:(.text+0x147f6a): undefined reference to `sdio_claim_irq'
gdm_sdio.c:(.text+0x148343): undefined reference to `sdio_writeb'
gdm_sdio.c:(.text+0x148352): undefined reference to `sdio_release_host'
sdio_boot.c:(.text+0x148543): undefined reference to `sdio_memcpy_toio'
sdio_boot.c:(.text+0x1485b7): undefined reference to `sdio_readb'
sdio_boot.c:(.text+0x14862c): undefined reference to `sdio_memcpy_fromio'
sdio_boot.c:(.text+0x14867d): undefined reference to `sdio_writeb'
sdio_boot.c:(.text+0x14869a): undefined reference to `sdio_writeb'
gdm_sdio.c:(.init.text+0xa6bc): undefined reference to `sdio_register_driver'
gdm_sdio.c:(.exit.text+0x23b6): undefined reference to `sdio_unregister_driver'


  parent reply	other threads:[~2013-04-29 16:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29  9:17 linux-next: Tree for Apr 29 Stephen Rothwell
2013-04-29 15:52 ` linux-next: Tree for Apr 29 (kvm) Randy Dunlap
2013-04-29 16:31   ` Gleb Natapov
2013-04-29 16:46     ` Paolo Bonzini
2013-04-29 17:01       ` Alex Williamson
2013-04-29 16:49     ` Alex Williamson
2013-04-29 16:05 ` [PATCH -next] proc_fs.h: fix build error when PROC_FS is not enabled Randy Dunlap
2013-04-30 16:36   ` David Rientjes
2013-04-30 17:40     ` Randy Dunlap
2013-04-29 16:05 ` [PATCH -next] tty.h: fix build errors " Randy Dunlap
2013-04-30 16:39   ` David Rientjes
2013-04-29 16:17 ` linux-next: Tree for Apr 29 (include/linux/proc_fs.h: proc_net_mkdir) Randy Dunlap
2013-04-29 16:25 ` linux-next: Tree for Apr 29 (kconfig) Randy Dunlap
2013-04-29 17:42   ` Yann E. MORIN
2013-04-29 16:42 ` Randy Dunlap [this message]
2013-04-29 16:51 ` linux-next: Tree for Apr 29 (sound/soc) Randy Dunlap
2013-04-29 17:13 ` linux-next: Tree for Apr 29 (many build errors when PROC_FS is not set -- part 1) Randy Dunlap
2013-04-29 20:05 ` linux-next: Tree for Apr 29 Randy Dunlap
2013-04-29 21:03   ` Randy Dunlap

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).