linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, linux-bluetooth@vger.kernel.org,
	jukka.rissanen@linux.intel.com,
	Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH bluetooth-next 0/6] 6lowpan: iphc defines and rework tc and flow label handling
Date: Tue, 20 Oct 2015 08:31:20 +0200	[thread overview]
Message-ID: <1445322686-2952-1-git-send-email-alex.aring@gmail.com> (raw)

Hi,

this patch series based on my previous series "[PATCH bluetooth-next 1/6]
mac802154: llsec: use kzfree" and contains changes for iphc defines and
reworking the tc/flow label handling.

I tested the tc/flow label handling with fakelb and wireshark. So it should
be wrong, when wireshark is wrong also. I hope wireshark has some correct
mechanism to handle it. I used "wireshark 1.12.7".

- Alex

Alexander Aring (6):
  6lowpan: nhc: move iphc manipulation out of nhc
  6lowpan: move IPHC functionality defines
  6lowpan: remove lowpan_is_addr_broadcast
  6lowpan: iphc: change define values
  6lowpan: rework tc and flow label handling
  6lowpan: put mcast compression in an own function

 include/net/6lowpan.h       | 133 -----------
 net/6lowpan/iphc.c          | 565 +++++++++++++++++++++++++++++++-------------
 net/6lowpan/nhc.c           |  13 +-
 net/6lowpan/nhc.h           |   9 +-
 net/6lowpan/nhc_udp.c       |  22 +-
 net/ieee802154/6lowpan/tx.c |   5 +-
 6 files changed, 430 insertions(+), 317 deletions(-)

-- 
2.6.1


             reply	other threads:[~2015-10-20  6:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  6:31 Alexander Aring [this message]
2015-10-20  6:31 ` [PATCH bluetooth-next 1/6] 6lowpan: nhc: move iphc manipulation out of nhc Alexander Aring
2015-10-20  6:31 ` [PATCH bluetooth-next 2/6] 6lowpan: move IPHC functionality defines Alexander Aring
2015-10-20  6:31 ` [PATCH bluetooth-next 3/6] 6lowpan: remove lowpan_is_addr_broadcast Alexander Aring
2015-10-20  6:31 ` [PATCH bluetooth-next 4/6] 6lowpan: iphc: change define values Alexander Aring
2015-10-20  6:31 ` [PATCH bluetooth-next 5/6] 6lowpan: rework tc and flow label handling Alexander Aring
2015-10-20  6:31 ` [PATCH bluetooth-next 6/6] 6lowpan: put mcast compression in an own function Alexander Aring
2015-10-20  8:06 ` [PATCH bluetooth-next 0/6] 6lowpan: iphc defines and rework tc and flow label handling Marcel Holtmann

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=1445322686-2952-1-git-send-email-alex.aring@gmail.com \
    --to=alex.aring@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).