From: "Arend van Spriel" <arend@broadcom.com>
To: "Borislav Petkov" <bp@alien8.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] brcmsmac: Fix build dep on LEDS_CLASS
Date: Sun, 17 Nov 2013 22:31:07 +0100 [thread overview]
Message-ID: <5289359B.8090506@broadcom.com> (raw)
In-Reply-To: <20131117133702.GA30840@pd.tnic>
On 11/17/13 14:37, Borislav Petkov wrote:
> From: Borislav Petkov<bp@suse.de>
>
> When building randconfigs with CONFIG_BCMA_DRIVER_GPIO=y, I get
>
> drivers/built-in.o: In function `brcms_led_unregister':
> (.text+0x351aca): undefined reference to `led_classdev_unregister'
> drivers/built-in.o: In function `brcms_led_register':
> (.text+0x351c65): undefined reference to `led_classdev_register'
>
> during the final linking stage because brcmsmac/led.c needs LEDS_CLASS
> for reg/dereg. Fix that.
Wouldn't it be better to fix it in brcmsmac.
Gr AvS
> Cc: "Rafał Miłecki"<zajec5@gmail.com>
> Cc: linux-wireless@vger.kernel.org
> Signed-off-by: Borislav Petkov<bp@suse.de>
> ---
>
> I'm attaching the .config in question.
>
> drivers/bcma/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/bcma/Kconfig b/drivers/bcma/Kconfig
> index 7c081b38ef3e..74dba9ca1413 100644
> --- a/drivers/bcma/Kconfig
> +++ b/drivers/bcma/Kconfig
> @@ -74,7 +74,7 @@ config BCMA_DRIVER_GMAC_CMN
>
> config BCMA_DRIVER_GPIO
> bool "BCMA GPIO driver"
> - depends on BCMA&& GPIOLIB
> + depends on BCMA&& GPIOLIB&& LEDS_CLASS
> help
> Driver to provide access to the GPIO pins of the bcma bus.
>
next prev parent reply other threads:[~2013-11-17 21:31 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 [this message]
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
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=5289359B.8090506@broadcom.com \
--to=arend@broadcom.com \
--cc=bp@alien8.de \
--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