[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB=NE6XS9-Zu9sb5geO2WTnnvv6KqyT+QnL5bRf1fiRx3=ocrg@mail.gmail.com>
Date: Thu, 24 Apr 2014 10:25:58 -0700
From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To: Alexander Aring <alex.aring@...il.com>
Cc: Alexander Smirnov <alex.bluesman.smirnov@...il.com>,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
linux-zigbee-devel@...ts.sourceforge.net,
David Miller <davem@...emloft.net>,
Johannes Berg <johannes@...solutions.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"backports@...r.kernel.org" <backports@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Linux-zigbee-devel] [PATCH] 6lowpan: nuke net_ieee802154_lowpan()
accessor when 6lowpan is disabled
On Thu, Apr 24, 2014 at 9:44 AM, Alexander Aring <alex.aring@...il.com> wrote:
> Hi,
>
> On Tue, Apr 22, 2014 at 12:03:58PM -0700, Luis R. Rodriguez wrote:
>> From: "Luis R. Rodriguez" <mcgrof@...e.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.
Thanks for the clarification, I actually did mean
CONFIG_IEEE802154_6LOWPAN however, I goofed that on the commit log.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists