Skip to contentSkip to conversation

sdio.c:undefined reference to `ssb_bus_unregister'

PATCH New Rafał Miłecki 2 participants 4 messages May 18, 2014 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 53781383.4VhTkq6xna8cylNO%[email protected]

#1 lore raw

PATCH 83/118 sdio.c:undefined reference to `ssb_bus_unregister'

Quoted 11 lines · kbuild test robot
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':

Quoted 1 line
Quoted 1 line

sdio.c:(.text+0x1460ff): undefined reference to `ssb_bus_unregister'

drivers/built-in.o: In function `b43_sdio_probe':

Quoted 1 line
Quoted 1 line

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

Does anyone has any idea what could go wrong?

Fengguang: please attach your bot's config.

Signature · 1 line
Rafa?
#2 lore raw

PATCH 83/118 sdio.c:undefined reference to `ssb_bus_unregister'

Quoted 20 lines · Rafa? Mi?ecki
Quoted 11 lines · kbuild test robot
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':

Quoted 1 line
Quoted 1 line

sdio.c:(.text+0x1460ff): undefined reference to `ssb_bus_unregister'

drivers/built-in.o: In function `b43_sdio_probe':

Quoted 1 line
Quoted 1 line

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

Quoted 3 lines

Does anyone has any idea what could go wrong?

Fengguang: please attach your bot's config.

Rafa?, the original email should have the .config attached.

Thanks,
Fengguang

#3 lore raw

PATCH 83/118 sdio.c:undefined reference to `ssb_bus_unregister'

Quoted 4 lines · Fengguang Wu
Quoted 1 line · Rafa? Mi?ecki

Fengguang: please attach your bot's config.

Rafa?, the original email should have the .config attached.

Oh, of course, I've no idea how I missed it. Sorry.

Btw. it seems your bot compiles kernel on DOS/Windows, or e-mail attachments are converted to DOS new line:
./.config: line 40: $'\r': command not found
make: *** [vmlinux] Error 127

Thanks for your bot/report, I've reproduced this issue!

Signature · 1 line
Rafa?
#4 lore raw

PATCH 83/118 sdio.c:undefined reference to `ssb_bus_unregister'

In reply to Rafał Miłecki
Quoted 11 lines · Rafa? Mi?ecki
Quoted 10 lines · kbuild test robot
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':

Quoted 1 line
Quoted 1 line

sdio.c:(.text+0x1460ff): undefined reference to `ssb_bus_unregister'

drivers/built-in.o: In function `b43_sdio_probe':

Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line

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