From: Alexander Aring <alex.aring@gmail.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: Simon Vincent <simon.vincent@xsilon.com>,
linux-wpan@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH linux-wpan v4] ieee802154: 6lowpan: ensure header compression does not corrupt ipv6 header
Date: Tue, 23 Sep 2014 11:35:45 +0200 [thread overview]
Message-ID: <20140923093544.GB12857@omega> (raw)
In-Reply-To: <20140923092653.GA12857@omega>
Jukka,
I/Simon mainly add you here in cc because this bug what Simon fixed here
is also inside of bluetooth 6lowpan.
I see now [0]. And it seems to me that this also occurs at bluetooth
branch. Do you have any questions on how the fix now is? Sorry, but I
need to clarify that you understood this issue and you/others prepare a
patch for this.
- Alex
[0] http://lxr.free-electrons.com/source/net/bluetooth/6lowpan.c#L509
next prev parent reply other threads:[~2014-09-23 9:35 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 [this message]
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
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=20140923093544.GB12857@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;
as well as URLs for NNTP newsgroup(s).