From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Lapin Subject: Re: [PATCH -next] ieee802154: fix kconfig bool/tristate muckup Date: Sat, 13 Jun 2009 14:57:54 +0400 Message-ID: <20090613105753.GB14520@build.ossfans.org> References: <20090611191420.1f4d5e4f.sfr@canb.auug.org.au> <4A31869B.3050901@oracle.com> <4A32DDC8.7060605@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4A32DDC8.7060605@oracle.com> Sender: linux-kernel-owner@vger.kernel.org To: Randy Dunlap Cc: David Miller , Stephen Rothwell , linux-next@vger.kernel.org, LKML , dbaryshkov@gmail.com, linux-zigbee-devel@lists.sourceforge.net, Netdev , Andrew Morton List-Id: linux-next.vger.kernel.org On Fri, Jun 12, 2009 at 03:59:20PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > 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 > Cc: linux-zigbee-devel@lists.sourceforge.net > Cc: Dmitry Eremin-Solenikov > Cc: Sergey Lapin Ackedy-by: Sergey Lapin Thanks a lot! S.