From: Alexander Aring <alex.aring@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de,
Alexander Aring <alex.aring@gmail.com>,
Jukka Rissanen <jukka.rissanen@linux.intel.com>,
Martin Townsend <mtownsend1973@gmail.com>
Subject: [PATCH bluetooth-next 0/2] 6lowpan: introduce nhc framework
Date: Sat, 29 Nov 2014 15:24:40 +0100 [thread overview]
Message-ID: <1417271082-10068-1-git-send-email-alex.aring@gmail.com> (raw)
This patch series introduce the next header compression framework. Currently
we support udp compression/uncompression only. This framework allow to add new
next header compression formats easily.
If somebody wants to add a new header compression format and some information
are missing while calling compression and uncompression callbacks. Please
feel free to make framework changes according these callbacks.
Cc: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: Martin Townsend <mtownsend1973@gmail.com>
Alexander Aring (2):
6lowpan: add generic nhc layer interface
6lowpan: add udp compression via nhc layer
net/6lowpan/Makefile | 5 +-
net/6lowpan/iphc.c | 188 +++++++-------------------------------------------
net/6lowpan/nhc.c | 183 ++++++++++++++++++++++++++++++++++++++++++++++++
net/6lowpan/nhc.h | 132 +++++++++++++++++++++++++++++++++++
net/6lowpan/nhc_udp.c | 173 ++++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 516 insertions(+), 165 deletions(-)
create mode 100644 net/6lowpan/nhc.c
create mode 100644 net/6lowpan/nhc.h
create mode 100644 net/6lowpan/nhc_udp.c
--
2.1.3
next reply other threads:[~2014-11-29 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 14:24 Alexander Aring [this message]
2014-11-29 14:24 ` [PATCH bluetooth-next 1/2] 6lowpan: add generic nhc layer interface Alexander Aring
2014-11-29 14:47 ` Marcel Holtmann
2014-11-29 15:03 ` Alexander Aring
2014-11-29 14:24 ` [PATCH bluetooth-next 2/2] 6lowpan: add udp compression via nhc layer 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=1417271082-10068-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 \
--cc=mtownsend1973@gmail.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