From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f48.google.com ([74.125.82.48]:41435 "EHLO mail-wg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752575AbaIWPgK (ORCPT ); Tue, 23 Sep 2014 11:36:10 -0400 Received: by mail-wg0-f48.google.com with SMTP id x13so1430616wgg.31 for ; Tue, 23 Sep 2014 08:36:09 -0700 (PDT) Date: Tue, 23 Sep 2014 17:36:03 +0200 From: Alexander Aring Subject: Re: [PATCH linux-wpan v4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header Message-ID: <20140923153601.GA16060@omega> References: <1411401123-7790-1-git-send-email-simon.vincent@xsilon.com> <20140922162148.GA7282@omega> <1411463634.4860.65.camel@jrissane-mobl.ger.corp.intel.com> <20140923092653.GA12857@omega> <20140923093544.GB12857@omega> <1411467246.4860.68.camel@jrissane-mobl.ger.corp.intel.com> <20140923103341.GA24710@omega> <75E2311D-E166-4891-B57B-390E5BFC8BB5@holtmann.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <75E2311D-E166-4891-B57B-390E5BFC8BB5@holtmann.org> Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Marcel Holtmann Cc: Jukka Rissanen , Simon Vincent , linux-wpan@vger.kernel.org Hi Marcel, On Tue, Sep 23, 2014 at 05:23:19PM +0200, Marcel Holtmann wrote: > Hi Alex, > > >>> I/Simon mainly add you here in cc because this bug what Simon fixed here > >>> is also inside of bluetooth 6lowpan. > >> > >> BTW, the v4 patch does not apply cleanly to bluetooth-next. The > >> modifications were very small thou. > >> > > > > It's a bug fix and should be go to wpan, then wpan goes to bluetooth. I > > know there is some easy solveable merge conflict... but maintainers need to be > > deal with it then. ;-) > > > > When this is an easy conflict it doesn't matter to wait on it. I hope > > that's okay for all maintainers, I am new in this handling. Maintainers > > isn't just "apply patches", making the right workflow and solve merge > > conflicts, I think. Otherwise some maintainer will tell me "don't making merge > > conflicts!", but I heard nothing something like that now. > > > > Or we wait when these changes are in bluetooth repo, which means also > > wpan repo. > > since 3.17 is basically around the corner, adding it to bluetooth tree is not getting us anywhere right now. So what I would do is include it in bluetooth-next and add a CC: stable tag to it. > you are right. I will try that to CC: stable on this patch. Please don't be angry that I will fail there. The last time when I tried it I got a formletter back. :-) - Alex