Hi Martin, On Tue, Nov 04, 2014 at 09:36:21PM +0000, Martin Townsend wrote: > Currently we ensure that the skb is freed on every error path in IPHC > decompression which makes it easy to introduce skb leaks. By centralising > the skb_free into the receive function it makes future decompression routines > easier to maintain. It does come at the expense of ensuring that the skb > passed into the decompression routine must not be copied. > I just want to give it a try and want to test it but I got a: error: patch failed: net/ieee802154/6lowpan_rtnl.c:200 error: net/ieee802154/6lowpan_rtnl.c: patch does not apply ... while applying. Is the patch really based on bluetooth-next [0]? Please respin this one if it doesn't break anything I will ack this one. - Alex [0] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git -- 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
