Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig
authorGustavo F. Padovan <padovan@profusion.mobi>
Sat, 26 Feb 2011 01:41:25 +0000 (22:41 -0300)
committerJohn W. Linville <linville@tuxdriver.com>
Mon, 28 Feb 2011 19:06:53 +0000 (14:06 -0500)
commitd45dcef77019012fc6769e657fc2f1a5d681bbbb
treeccc784f81c4d261cff12a872ebf8c77ca507daa5
parentf54b92b9272cde9720b1371937928e92c5b29fb4
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>
net/bluetooth/Kconfig