From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 19 Aug 2014 18:51:38 +0200 From: Alexander Aring To: Marcel Holtmann Cc: BlueZ development , linux-wpan@vger.kernel.org, kernel@pengutronix.de Subject: Re: [PATCH bluetooth 0/5] mac802154: ieee802154: stable patches Message-ID: <20140819165136.GB1116@omega> References: <1408438983-13892-1-git-send-email-alex.aring@gmail.com> <79B561AB-5717-4F81-9725-FDA13BC2A789@holtmann.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <79B561AB-5717-4F81-9725-FDA13BC2A789@holtmann.org> List-ID: Hi Marcel, On Tue, Aug 19, 2014 at 11:44:11AM -0500, Marcel Holtmann wrote: > Hi Alex, > > > these patches contains patches for the bluetooth branch. > > > > This series includes memory leak fixes and an errno value fix. > > Also there are two patches for sending and receiving 1280 6LoWPAN packets, > > which makes the IEEE 802.15.4 6LoWPAN stack more RFC compliant. > > > > - Alex > > > > Alexander Aring (2): > > ieee802154: 6lowpan_rtnl: fix correct errno value > > ieee802154: 6lowpan: ensure of sending 1280 packets > > > > Martin Townsend (3): > > mac802154: fixed potential skb leak with mac802154_parse_frame_start > > ieee802154: mac802154: handle the reserved dest mode by dropping the > > packet > > ieee802154: 6lowpan: ensure MTU of 1280 for 6lowpan > > > > include/net/netns/ieee802154_6lowpan.h | 1 - > > net/ieee802154/6lowpan_rtnl.c | 4 ++-- > > net/ieee802154/reassembly.c | 13 +++---------- > > net/mac802154/wpan.c | 6 +++++- > > 4 files changed, 10 insertions(+), 14 deletions(-) > > all 5 patches have been applied to bluetooth tree. > > However is it possible you introduced a compile warning. > > CC net/ieee802154/reassembly.o > net/ieee802154/reassembly.c: In function ‘lowpan_frag_rcv’: > net/ieee802154/reassembly.c:358:34: warning: unused variable ‘ieee802154_lowpan’ [-Wunused-variable] > struct netns_ieee802154_lowpan *ieee802154_lowpan = > ^ indeed, I will send a v2 of this series. Sorry. I will integrate the "compile warning check" in my workflow for the next time. Thanks. - Alex