[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A32DDC8.7060605@oracle.com>
Date: Fri, 12 Jun 2009 15:59:20 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: David Miller <davem@...emloft.net>
CC: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
dbaryshkov@...il.com, slapin@...fans.org,
linux-zigbee-devel@...ts.sourceforge.net,
Netdev <netdev@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH -next] ieee802154: fix kconfig bool/tristate muckup
From: Randy Dunlap <randy.dunlap@...cle.com>
menuconfig IEEE802154_DRIVERS is a bool that depends on tristate IEEE802154.
If the IEEE802154 symbol is 'm', the bool becomes 'y'.
This allows tristate symbols under IEEE802154_DRIVERS to be configured as
'y' and cause build problems.
Changing the menuconfig bool to a tristate fixes this.
drivers/built-in.o: In function `fake_scan_req':
fakehard.c:(.text+0x46d625): undefined reference to `ieee802154_nl_scan_confirm'
drivers/built-in.o: In function `fake_disassoc_req':
fakehard.c:(.text+0x46d66f): undefined reference to `ieee802154_nl_disassoc_confirm'
drivers/built-in.o: In function `fake_assoc_req':
fakehard.c:(.text+0x46d6be): undefined reference to `ieee802154_nl_assoc_confirm'
Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
Cc: linux-zigbee-devel@...ts.sourceforge.net
Cc: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
Cc: Sergey Lapin <slapin@...fans.org>
---
drivers/ieee802154/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20090612.orig/drivers/ieee802154/Kconfig
+++ linux-next-20090612/drivers/ieee802154/Kconfig
@@ -1,5 +1,5 @@
menuconfig IEEE802154_DRIVERS
- bool "IEEE 802.15.4 drivers"
+ tristate "IEEE 802.15.4 drivers"
depends on NETDEVICES && IEEE802154
default y
---help---
--
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists