From: Borislav Petkov <bp@alien8.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] brcmsmac: Fix build dep on LEDS_CLASS
Date: Tue, 19 Nov 2013 00:32:47 +0100 [thread overview]
Message-ID: <20131118233247.GM24851@pd.tnic> (raw)
In-Reply-To: <528A925C.20602@broadcom.com>
On Mon, Nov 18, 2013 at 11:19:08PM +0100, Arend van Spriel wrote:
> what about:
>
> config BRCMSMAC
> tristate "Broadcom IEEE802.11n PCIe SoftMAC WLAN driver"
> depends on MAC80211
> depends on BCMA_POSSIBLE
> + select LEDS_CLASS if BCMA_DRIVER_GPIO
> select BCMA
I know, nice and short but too good to be true. LEDS_CLASS needs to pull
in NEW_LEDS unfortunately:
drivers/built-in.o: In function `set_brightness_delayed':
led-class.c:(.text+0x4596e5): undefined reference to `led_stop_software_blink'
drivers/built-in.o: In function `led_classdev_register':
(.text+0x4598db): undefined reference to `leds_list_lock'
drivers/built-in.o: In function `led_classdev_register':
(.text+0x4598e7): undefined reference to `leds_list'
drivers/built-in.o: In function `led_classdev_register':
(.text+0x4598f3): undefined reference to `leds_list'
drivers/built-in.o: In function `led_classdev_register':
(.text+0x4598fa): undefined reference to `leds_list_lock'
drivers/built-in.o: In function `led_classdev_register':
(.text+0x459901): undefined reference to `leds_list'
drivers/built-in.o: In function `led_classdev_unregister':
(.text+0x4599a8): undefined reference to `led_stop_software_blink'
drivers/built-in.o: In function `led_classdev_unregister':
(.text+0x4599b2): undefined reference to `led_set_brightness'
drivers/built-in.o: In function `led_classdev_unregister':
(.text+0x4599c2): undefined reference to `leds_list_lock'
drivers/built-in.o: In function `led_classdev_unregister':
(.text+0x4599d6): undefined reference to `leds_list_lock'
make: *** [vmlinux] Error 1
What works, instead, is below. I think my "depends" solution from
earlier takes care of this without you having to select other stuff
explicitly but in the end of the day, I don't really care all that much
which one you guys take.
--
diff --git a/drivers/net/wireless/brcm80211/Kconfig b/drivers/net/wireless/brcm80211/Kconfig
index b00a7e92225f..54e36fcb3954 100644
--- a/drivers/net/wireless/brcm80211/Kconfig
+++ b/drivers/net/wireless/brcm80211/Kconfig
@@ -5,6 +5,8 @@ config BRCMSMAC
tristate "Broadcom IEEE802.11n PCIe SoftMAC WLAN driver"
depends on MAC80211
depends on BCMA
+ select NEW_LEDS if BCMA_DRIVER_GPIO
+ select LEDS_CLASS if BCMA_DRIVER_GPIO
select BRCMUTIL
select FW_LOADER
select CRC_CCITT
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-11-18 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 13:37 [PATCH] brcmsmac: Fix build dep on LEDS_CLASS Borislav Petkov
2013-11-17 21:31 ` Arend van Spriel
2013-11-17 23:02 ` Borislav Petkov
2013-11-18 11:58 ` Rafał Miłecki
2013-11-18 13:32 ` Borislav Petkov
2013-11-18 20:40 ` Borislav Petkov
2013-11-18 22:19 ` Arend van Spriel
2013-11-18 23:32 ` Borislav Petkov [this message]
2013-11-19 9:11 ` Arend van Spriel
2013-11-19 10:36 ` Borislav Petkov
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=20131118233247.GM24851@pd.tnic \
--to=bp@alien8.de \
--cc=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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