From: Alexander Aring <alex.aring@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: alex.bluesman.smirnov@gmail.com, dbaryshkov@gmail.com,
linux-zigbee-devel@lists.sourceforge.net, davem@davemloft.net,
Johannes Berg <johannes@sipsolutions.net>,
netdev@vger.kernel.org, backports@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-zigbee-devel] [PATCH] 6lowpan: nuke net_ieee802154_lowpan() accessor when 6lowpan is disabled
Date: Thu, 24 Apr 2014 18:44:48 +0200 [thread overview]
Message-ID: <20140424164445.GA4675@omega> (raw)
In-Reply-To: <1398193438-23805-1-git-send-email-mcgrof@do-not-panic.com>
Hi,
On Tue, Apr 22, 2014 at 12:03:58PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>
> Johannes noted this is not needed, all of the fragment
> accessors don't need CONFIG_NET_NS. This goes test compiled with
> CONFIG_BT_6LOWPAN=y and a disabled CONFIG_NET_NS.
>
a little note about this here. There exists two 6LoWPAN standard. One
for bluetooth low energy and one for IEEE 802.15.4.
The actual namespace is only for IEEE 802.15.4, because we need
fragmentation there. 6LoWPAN fragmentation for bluetooth low energy is
already handled by the MAC-Layer. So this has nothing to do with
CONFIG_BT_6LOWPAN.
- Alex
next prev parent reply other threads:[~2014-04-24 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 19:03 [PATCH] 6lowpan: nuke net_ieee802154_lowpan() accessor when 6lowpan is disabled Luis R. Rodriguez
2014-04-24 16:36 ` David Miller
2014-04-24 16:44 ` Alexander Aring [this message]
2014-04-24 17:25 ` [Linux-zigbee-devel] " Luis R. Rodriguez
2014-04-24 17:33 ` Alexander Aring
2014-04-24 17:57 ` Luis R. Rodriguez
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=20140424164445.GA4675@omega \
--to=alex.aring@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=backports@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dbaryshkov@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=mcgrof@do-not-panic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox