From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, Jukka Rissanen <jukka.rissanen@linux.intel.com>
Subject: Re: [PATCH bluetooth-next 0/7] ieee802154: 6lowpan: remove full-size calculation workarounds
Date: Thu, 25 Dec 2014 12:30:49 +0100 [thread overview]
Message-ID: <20141225113047.GA27009@omega> (raw)
In-Reply-To: <1419344909-16007-1-git-send-email-alex.aring@gmail.com>
Marcel,
please drop this series. I reconsider my change and detect that IPHC
uncompression use "uh->len = htons(skb->len + sizeof(struct udphdr))"
for udp next header compression.
This patch introduce now a iphc uncompression after first fragment and
skb->len isn't the full payload there. Need to look how we can deal with
that now. I really like to remove these workarounds to run a 6LoWPAN
header parse twice.
When the first fragment arrived we know the full payload but we can't
set skb->len with this value.
Need to look for another solution for this which can be used by btle
and 802154 6LoWPAN.
- Alex
prev parent reply other threads:[~2014-12-25 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 14:28 [PATCH bluetooth-next 0/7] ieee802154: 6lowpan: remove full-size calculation workarounds Alexander Aring
2014-12-23 14:28 ` [PATCH bluetooth-next 1/7] 6lowpan: allow pull only at lowpan_fetch_skb Alexander Aring
2014-12-23 14:28 ` [PATCH bluetooth-next 2/7] ieee802154: 6lowpan: skb_pull with error handling Alexander Aring
2014-12-23 14:28 ` [PATCH bluetooth-next 3/7] ieee802154: 6lowpan: use skb_network_header Alexander Aring
2014-12-23 14:28 ` [PATCH bluetooth-next 4/7] ieee802154: 6lowpan: remove rx full-size calc workaround Alexander Aring
2014-12-23 14:28 ` [PATCH bluetooth-next 5/7] ieee802154: 6lowpan: handle fragmented IPv6 Alexander Aring
2014-12-23 14:28 ` [PATCH bluetooth-next 6/7] ieee802154: 6lowpan: cleanup frag dispatch cases Alexander Aring
2014-12-23 14:28 ` [PATCH bluetooth-next 7/7] ieee802154: 6lowpan: remove tx full-size calc workaround Alexander Aring
2014-12-25 11:30 ` Alexander Aring [this message]
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=20141225113047.GA27009@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
/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