Hi Stephen,
> It's now built as a separate utility module, and enabling BT selects
> that module in Kconfig. This fixes:
>
> net/ieee802154/built-in.o:(___ksymtab_gpl+lowpan_process_data+0x0): multiple
> definition of `__ksymtab_lowpan_process_data'
> net/bluetooth/built-in.o:(___ksymtab_gpl+lowpan_process_data+0x0): first
> defined here
> net/ieee802154/built-in.o:(___ksymtab_gpl+lowpan_header_compress+0x0):
> multiple definition of `__ksymtab_lowpan_header_compress'
> net/bluetooth/built-in.o:(___ksymtab_gpl+lowpan_header_compress+0x0): first
> defined here
> net/ieee802154/built-in.o: In function `lowpan_header_compress':
> net/ieee802154/6lowpan_iphc.c:606: multiple definition of
> `lowpan_header_compress'
> net/bluetooth/built-in.o:/home/swarren/shared/git_wa/kernel/kernel.git/net/bluetooth/../ieee802154/6lowpan_iphc.c:606:
> first defined here
> net/ieee802154/built-in.o: In function `lowpan_process_data':
> net/ieee802154/6lowpan_iphc.c:344: multiple definition of
> `lowpan_process_data'
> net/bluetooth/built-in.o:/home/swarren/shared/git_wa/kernel/kernel.git/net/bluetooth/../ieee802154/6lowpan_iphc.c:344:
> first defined here
> make[1]: *** [net/built-in.o] Error 1
>
> (this change probably simply wasn't "git add"d to a53d34c3465b)
>
> Fixes: a53d34c3465b ("net: move 6lowpan compression code to separate module")
> Fixes: 18722c247023 ("Bluetooth: Enable 6LoWPAN support for BT LE devices")
> Signed-off-by: Stephen Warren <[email protected]>
seems that I missed the initial patch that changes this to build this as
separate module. Please CC [email protected] so that we do not
accidentally miss these changes.
Our initial idea was to create net/core/6lowpan_iphc.c or maybe
net/6lowpan/iphc.c module to make it clear that this is independent from IEEE
802.15.4 and Bluetooth. However we started to do this inside net/ieee802154 to
this started.
Should we do the change now and move it into its separate directory.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
