From: Kalle Valo <kvalo@qca.qualcomm.com>
To: linville@tuxdriver.com
Cc: ath6kl-devel@qualcomm.com, linux-wireless@vger.kernel.org
Subject: [PATCH] ath6kl: force building as a module
Date: Wed, 04 Jan 2012 11:41:34 +0200 [thread overview]
Message-ID: <20120104094134.28754.39652.stgit@x201> (raw)
Stephen reported that ath6kl fails if both sdio and usb are built
into the kernel:
ath6kl/cfg80211.c:27:1: error: expected ')' before 'KBUILD_MODNAME'
ath6kl/cfg80211.c:27:1: error: 'KBUILD_MODNAME' undeclared here (not in a function)
ath6kl/cfg80211.c:27:1: error: expected ',' or ';' before string constant
As a temporary fix make ath6kl build only as a module. This will be reverted
once a separate ath6kl core module is implemented which will fix this
properly.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
---
drivers/net/wireless/ath/ath6kl/Kconfig | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath6kl/Kconfig b/drivers/net/wireless/ath/ath6kl/Kconfig
index d755a5e..d290ec7 100644
--- a/drivers/net/wireless/ath/ath6kl/Kconfig
+++ b/drivers/net/wireless/ath/ath6kl/Kconfig
@@ -6,6 +6,7 @@ config ATH6KL_SDIO
depends on ATH6KL
depends on MMC
depends on CFG80211
+ depends on m
---help---
This module adds support for wireless adapters based on
Atheros AR6003 and AR6004 chipsets running over SDIO. If you
@@ -19,6 +20,7 @@ config ATH6KL_USB
depends on USB
depends on CFG80211
depends on EXPERIMENTAL
+ depends on m
---help---
This module adds support for wireless adapters based on
Atheros AR6004 chipset running over USB. This is still under
next reply other threads:[~2012-01-04 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:41 Kalle Valo [this message]
2012-01-04 9:48 ` [PATCH] ath6kl: force building as a module Kalle Valo
2012-01-04 9:48 ` Kalle Valo
[not found] ` <4F042078.5040902-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>
2012-01-04 18:28 ` David Miller
2012-01-04 18:28 ` David Miller
2012-01-04 18:28 ` David Miller
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=20120104094134.28754.39652.stgit@x201 \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.