b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: [wireless-next:master 83/118] sdio.c:undefined reference to `ssb_bus_unregister'
Date: Sun, 18 May 2014 13:23:17 +0200	[thread overview]
Message-ID: <CACna6rw8vSmrAFWJSDRiwYv9-Ywws8v6NMLYWE45F0r_4xtziA@mail.gmail.com> (raw)
In-Reply-To: <CACna6rz6GQ62RL0eZufvp=f=zp93WRdRQduVn9vaO5d-MVEBWg@mail.gmail.com>

On 18 May 2014 11:01, Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> On 18 May 2014 03:57, kbuild test robot <fengguang.wu@intel.com> wrote:
>> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git master
>> head:   f8b8a47e06a0d07219629c83de2a3b7ff1d5aa65
>> commit: fbe057d8a185d4b588bd5dc18ea43fd12ce3d689 [83/118] b43: drop SSB dependency
>> config: x86_64-randconfig-iv0-05180939 (attached as .config)
>>
>> All error/warnings:
>>
>>    drivers/built-in.o: In function `b43_sdio_remove':
>>>> sdio.c:(.text+0x1460ff): undefined reference to `ssb_bus_unregister'
>>    drivers/built-in.o: In function `b43_sdio_probe':
>>>> sdio.c:(.text+0x1462af): undefined reference to `ssb_bus_sdiobus_register'
>
> I don't understand what's going on there :(
> 1) sdio.c is compiled if we have CONFIG_B43_SDIO
> 2) a) B43_SDIO depends on SSB_SDIOHOST_POSSIBLE
> 2) b) SSB_SDIOHOST_POSSIBLE depends on SSB
> 3) a) B43_SDIO selects SSB_SDIOHOST
> 3) b) SSB_SDIOHOST gives us ssb_bus_sdiobus_register

Oh, there goes an answer:
CONFIG_B43=y
CONFIG_SSB=m

Above was possible because of:
# CONFIG_B43_BUSES_SSB is not set

      parent reply	other threads:[~2014-05-18 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53781383.4VhTkq6xna8cylNO%fengguang.wu@intel.com>
2014-05-18  9:01 ` [wireless-next:master 83/118] sdio.c:undefined reference to `ssb_bus_unregister' Rafał Miłecki
2014-05-18  9:17   ` Fengguang Wu
2014-05-18 11:13     ` Rafał Miłecki
2014-05-18 11:23   ` Rafał Miłecki [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=CACna6rw8vSmrAFWJSDRiwYv9-Ywws8v6NMLYWE45F0r_4xtziA@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=b43-dev@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).