From: Simon Wunderlich <sw@simonwunderlich.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
mathias.kretschmer@fokus.fraunhofer.de,
Simon Wunderlich <sw@simonwunderlich.de>
Subject: [net-next v4 0/3] 802.21 and MPLS headers and classification
Date: Mon, 3 Mar 2014 17:23:09 +0100 [thread overview]
Message-ID: <1393863792-18172-1-git-send-email-sw@simonwunderlich.de> (raw)
this series contains a header file proposal for MPLS labels. These
labels do not seem to be properly defined in the kernel so far. We are
developing a wired/wireless 802.21/MPLS switch and need to check the
MPLS labels to use the traffic control info for transmissions over
802.11 networks.
Changes to third version:
* rename mpls_label_stack to mpls_label (thanks Neil)
* fix over-indendented closing brac (thanks Sergei)
* add Johannes' Ack
Thanks,
Simon
Simon Wunderlich (3):
if_ether.h: add IEEE 802.21 Ethertype
UAPI: add MPLS label stack definition
cfg80211: add MPLS and 802.21 classification
include/linux/mpls.h | 6 ++++++
include/uapi/linux/if_ether.h | 1 +
include/uapi/linux/mpls.h | 34 ++++++++++++++++++++++++++++++++++
net/wireless/util.c | 16 ++++++++++++++++
4 files changed, 57 insertions(+)
create mode 100644 include/linux/mpls.h
create mode 100644 include/uapi/linux/mpls.h
--
1.7.10.4
next reply other threads:[~2014-03-03 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 16:23 Simon Wunderlich [this message]
2014-03-03 16:23 ` [net-next v4 1/3] if_ether.h: add IEEE 802.21 Ethertype Simon Wunderlich
2014-03-03 16:23 ` [net-next v4 2/3] UAPI: add MPLS label stack definition Simon Wunderlich
2014-03-03 16:23 ` [net-next v4 3/3] cfg80211: add MPLS and 802.21 classification Simon Wunderlich
2014-03-04 18:51 ` [net-next v4 0/3] 802.21 and MPLS headers and classification David Miller
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=1393863792-18172-1-git-send-email-sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=netdev@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).