Bluetooth: make sure 6LOWPAN_IPHC is built-in if needed
Commit 975508879
"Bluetooth: make bluetooth 6lowpan as an option"
ensures that 6LOWPAN_IPHC is turned on when we have BT_6LOWPAN
enabled in Kconfig, but it allows building the IPHC code as
a loadable module even if the entire Bluetooth stack is built-in,
and that causes a link error.
We can solve that by moving the 'select' statement into CONFIG_BT,
which is a "tristate" option to enforce that 6LOWPAN_IPHC can
only be a module if BT also is a module.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
parent
dcf4adbfdc
commit
52d3ef5c25
1 changed files with 1 additions and 1 deletions
|
@ -6,6 +6,7 @@ menuconfig BT
|
|||
tristate "Bluetooth subsystem support"
|
||||
depends on NET && !S390
|
||||
depends on RFKILL || !RFKILL
|
||||
select 6LOWPAN_IPHC if BT_6LOWPAN
|
||||
select CRC16
|
||||
select CRYPTO
|
||||
select CRYPTO_BLKCIPHER
|
||||
|
@ -42,7 +43,6 @@ menuconfig BT
|
|||
config BT_6LOWPAN
|
||||
bool "Bluetooth 6LoWPAN support"
|
||||
depends on BT && IPV6
|
||||
select 6LOWPAN_IPHC
|
||||
help
|
||||
IPv6 compression over Bluetooth.
|
||||
|
||||
|
|
Loading…
Reference in a new issue