netdev - Re: [PATCH net-next v2] 6lowpan: Moving generic compression code into 6lowpan

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Dec 2013 13:12:10 +0100
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Alexander Aring <alex.aring@...il.com>
Cc:	Jukka Rissanen <jukka.rissanen@...ux.intel.com>,
	netdev@...r.kernel.org, linux-zigbee-devel@...ts.sourceforge.net
Subject: Re: [PATCH net-next v2] 6lowpan: Moving generic compression code into 6lowpan_iphc.c

Hi Alexander,

> thanks for working on this! Now my acked-by is correct, sry. Didn't
> catch the debug output at first time.
> 
>> Because the IEEE 802154 and Bluetooth share the IP header compression
>> and uncompression code, the common code is moved to 6lowpan_iphc.c
>> file.
>> 
>> Signed-off-by: Jukka Rissanen <jukka.rissanen@...ux.intel.com>
>> ---
> 
> Acked-by: Alexander Aring <alex.aring@...il.com>

are you fine with us carrying these patches through bluetooth-next tree.

Dave, or do you want to merge this one into net-next and then we have wireless-next pulling that in.

I am trying to figure out on how we get this handled with the minimum of conflicts during the next merge window. And also at the same time get enough exposure via linux-next. The Bluetooth part is getting ready to be pushed into bluetooth-next.

Regards

Marcel

--
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