From: Alexander Aring <alex.aring@gmail.com>
To: alex.bluesman.smirnov@gmail.com
Cc: dbaryshkov@gmail.com, davem@davemloft.net,
linux-zigbee-devel@lists.sourceforge.net, netdev@vger.kernel.org,
martin.townsend@xsilon.com,
Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH net-next v2 5/6] net: ns: add ieee802154_6lowpan namespace
Date: Fri, 21 Feb 2014 19:59:01 +0100 [thread overview]
Message-ID: <1393009142-1694-6-git-send-email-alex.aring@gmail.com> (raw)
In-Reply-To: <1393009142-1694-1-git-send-email-alex.aring@gmail.com>
This patch adds necessary ieee802154 6lowpan namespace to provide the
inet_frag information. This is a initial support for handling 6lowpan
fragmentation with the inet_frag api.
Signed-off-by: Alexander Aring <alex.aring@gmail.com>
Tested-by: Martin Townsend <martin.townsend@xsilon.com>
---
include/net/net_namespace.h | 4 ++++
include/net/netns/ieee802154_6lowpan.h | 13 +++++++++++++
2 files changed, 17 insertions(+)
create mode 100644 include/net/netns/ieee802154_6lowpan.h
diff --git a/include/net/net_namespace.h b/include/net/net_namespace.h
index 991dcd9..79387f7 100644
--- a/include/net/net_namespace.h
+++ b/include/net/net_namespace.h
@@ -15,6 +15,7 @@
#include <net/netns/packet.h>
#include <net/netns/ipv4.h>
#include <net/netns/ipv6.h>
+#include <net/netns/ieee802154_6lowpan.h>
#include <net/netns/sctp.h>
#include <net/netns/dccp.h>
#include <net/netns/netfilter.h>
@@ -90,6 +91,9 @@ struct net {
#if IS_ENABLED(CONFIG_IPV6)
struct netns_ipv6 ipv6;
#endif
+#if IS_ENABLED(CONFIG_IEEE802154_6LOWPAN)
+ struct netns_ieee802154_lowpan ieee802154_lowpan;
+#endif
#if defined(CONFIG_IP_SCTP) || defined(CONFIG_IP_SCTP_MODULE)
struct netns_sctp sctp;
#endif
diff --git a/include/net/netns/ieee802154_6lowpan.h b/include/net/netns/ieee802154_6lowpan.h
new file mode 100644
index 0000000..88110b7
--- /dev/null
+++ b/include/net/netns/ieee802154_6lowpan.h
@@ -0,0 +1,13 @@
+/*
+ * ieee802154 6lowpan in net namespaces
+ */
+
+#include <net/inet_frag.h>
+
+#ifndef __NETNS_IEEE802154_6LOWPAN_H__
+#define __NETNS_IEEE802154_6LOWPAN_H__
+
+struct netns_ieee802154_lowpan {
+};
+
+#endif
--
1.9.0
next prev parent reply other threads:[~2014-02-21 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 18:58 [PATCH net-next v2 0/6] 6lowpan: reimplementation of fragmentation handling Alexander Aring
2014-02-21 18:58 ` [PATCH net-next v2 1/6] 6lowpan: add frag information struct Alexander Aring
2014-02-21 18:58 ` [PATCH net-next v2 2/6] 6lowpan: fix fragmentation on sending side Alexander Aring
2014-02-24 23:52 ` David Miller
2014-02-25 1:21 ` Alexander Aring
2014-02-25 1:31 ` David Miller
2014-02-25 2:38 ` Alexander Aring
2014-02-21 18:58 ` [PATCH net-next v2 3/6] 6lowpan: move 6lowpan.c to 6lowpan_rtnl.c Alexander Aring
[not found] ` <1393009142-1694-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-21 18:59 ` [PATCH net-next v2 4/6] 6lowpan: fix some checkpatch issues Alexander Aring
2014-02-21 18:59 ` Alexander Aring [this message]
2014-02-21 18:59 ` [PATCH net-next v2 6/6] 6lowpan: handling 6lowpan fragmentation via inet_frag api 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=1393009142-1694-6-git-send-email-alex.aring@gmail.com \
--to=alex.aring@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=davem@davemloft.net \
--cc=dbaryshkov@gmail.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=martin.townsend@xsilon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.