From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Jukka Rissanen <jukka.rissanen@linux.intel.com>,
Simon Vincent <simon.vincent@xsilon.com>,
linux-wpan@vger.kernel.org
Subject: Re: [PATCH linux-wpan v4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header
Date: Tue, 23 Sep 2014 17:36:03 +0200 [thread overview]
Message-ID: <20140923153601.GA16060@omega> (raw)
In-Reply-To: <75E2311D-E166-4891-B57B-390E5BFC8BB5@holtmann.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
next prev parent reply other threads:[~2014-09-23 15:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 15:52 [PATCH linux-wpan v4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header Simon Vincent
2014-09-22 16:21 ` Alexander Aring
2014-09-22 17:02 ` Alexander Aring
2014-09-23 9:13 ` Jukka Rissanen
2014-09-23 9:26 ` Alexander Aring
2014-09-23 9:35 ` Alexander Aring
2014-09-23 10:14 ` Jukka Rissanen
2014-09-23 10:33 ` Alexander Aring
2014-09-23 10:45 ` Jukka Rissanen
2014-09-23 15:23 ` Marcel Holtmann
2014-09-23 15:36 ` Alexander Aring [this message]
2014-09-23 16:19 ` Marcel Holtmann
2014-09-24 9:47 ` Alexander Aring
2014-09-24 9:55 ` Marcel Holtmann
2014-09-24 10:04 ` Alexander Aring
2014-09-24 12:24 ` Marcel Holtmann
2014-09-24 12:49 ` Alexander Aring
2014-09-23 14:20 ` Jukka Rissanen
2014-09-23 14:43 ` Alexander Aring
2014-09-23 15:03 ` Alexander Aring
2014-09-24 7:10 ` Jukka Rissanen
2014-09-24 7:11 ` Alexander Aring
2014-09-23 10:16 ` Jukka Rissanen
2014-09-22 17:20 ` Alexander Aring
2014-09-24 9:50 ` Alexander Aring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140923153601.GA16060@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=simon.vincent@xsilon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox