Hi Geert, >>> Change config symbol 6LOWPAN from type bool to type tristate, so >>> 6LoWPAN can be built modular, just like IPV6 >>> >>> Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> >>> --- >>> net/6lowpan/Kconfig | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/net/6lowpan/Kconfig b/net/6lowpan/Kconfig >>> index 028a5c6d1f61..e4a02ef55102 100644 >>> --- a/net/6lowpan/Kconfig >>> +++ b/net/6lowpan/Kconfig >>> @@ -1,5 +1,5 @@ >>> config 6LOWPAN >>> - bool "6LoWPAN Support" >>> + tristate "6LoWPAN Support" >> >> is this a regression from the previous CONFIG_6LOWPAN separation that we introduced? If it is, then it might be easiest if Dave just takes it into his net tree. Otherwise I take it through bluetooth-next. > > I hadn't thought about that... Checking... > > Yes, I believe this is a regression. > > In v3.16, my allmodconfig build had: > > CONFIG_IEEE802154_6LOWPAN=m > CONFIG_6LOWPAN_IPHC=m > CONFIG_BT_6LOWPAN=y > > Without my patch it has: > > CONFIG_6LOWPAN=y > CONFIG_IEEE802154_6LOWPAN=m > CONFIG_BT_6LOWPAN=m > > and iphc is what's in net/6lowpan/built-in.o now. Acked-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> Dave, I am fine if you just queue this up for 3.17-rc1. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
