netdev - Re: [RFC net-next] 6lowpan: Moving generic parts into net/core/6lowpan.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 20 Nov 2013 14:58:04 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jukka.rissanen@...ux.intel.com
Cc:	netdev@...r.kernel.org, alex.aring@...il.com
Subject: Re: [RFC net-next] 6lowpan: Moving generic parts into
 net/core/6lowpan.c

From: Jukka Rissanen <jukka.rissanen@...ux.intel.com>
Date: Wed, 20 Nov 2013 14:34:09 +0200

> Because the IEEE 802154 and Bluetooth 6LoWPAN share the IPv6
> header compression and uncompression code, the common code
> is moved to net/core/6lowpan.c file.
> 
> Signed-off-by: Jukka Rissanen <jukka.rissanen@...ux.intel.com>

There is no reason to move this file out from net/ieee802154/

Just like ipv6 does, you can have a net/ieee802154/6lowpan_core.c
file and appropriate Kconfig/Makefile rules to split this functionality
out appropriately.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html