From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-wireless@vger.kernel.org,
mathias.kretschmer@fokus.fraunhofer.de
Subject: Re: [net-next v3 3/3] cfg80211: add MPLS and 802.21 classification
Date: Mon, 24 Feb 2014 13:33:48 +0100 [thread overview]
Message-ID: <1393245228.4190.14.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1393244920-15903-4-git-send-email-sw@simonwunderlich.de> (sfid-20140224_132903_316161_47795452)
On Mon, 2014-02-24 at 13:28 +0100, Simon Wunderlich wrote:
> MPLS labels may contain traffic control information, which should be
> evaluated and used by the wireless subsystem if present.
>
> Also check for IEEE 802.21 which is always network control traffic.
Fine with me. I guess this should go through net-next due to the
dependencies on patches 1 and 2.
> Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
> Signed-off-by: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
johannes
next prev parent reply other threads:[~2014-02-24 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 12:28 [net-next v3 0/3] 802.21 and MPLS headers and classification Simon Wunderlich
2014-02-24 12:28 ` [net-next v3 1/3] if_ether.h: add IEEE 802.21 Ethertype Simon Wunderlich
2014-02-24 12:28 ` [net-next v3 2/3] UAPI: add MPLS label stack definition Simon Wunderlich
2014-02-25 9:53 ` Neil Jerram
[not found] ` <1393244920-15903-1-git-send-email-sw-2YrNx6rUIHYiY0qSoAWiAoQuADTiUCJX@public.gmane.org>
2014-02-24 12:28 ` [net-next v3 3/3] cfg80211: add MPLS and 802.21 classification Simon Wunderlich
2014-02-24 12:33 ` Johannes Berg [this message]
2014-02-24 19:57 ` Sergei Shtylyov
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=1393245228.4190.14.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
/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).