Gustavo F. Padovan d45dcef770 Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig ... If we want something "bool" built-in in something "tristate" it can't "depend on" the tristate config option. Report by DaveM: I give it 'y' just to make it happen, for both, and afterways no matter how many times I rerun "make oldconfig" I keep seeing things like this in my build: scripts/kconfig/conf --silentoldconfig Kconfig include/config/auto.conf:986:warning: symbol value 'm' invalid for BT_SCO include/config/auto.conf:3156:warning: symbol value 'm' invalid for BT_L2CAP Reported-by: David S. Miller <davem@davemloft.net> Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi> Signed-off-by: John W. Linville <linville@tuxdriver.com>		2011-02-28 14:06:53 -05:00
..
bnep
cmtp
hidp
rfcomm
af_bluetooth.c
hci_conn.c
hci_core.c
hci_event.c
hci_sock.c
hci_sysfs.c
Kconfig
l2cap_core.c
l2cap_sock.c
lib.c
Makefile
mgmt.c
sco.c