From: Marcel Holtmann <marcel@holtmann.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alexander Aring <alex.aring@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
linux-zigbee-devel@lists.sourceforge.net,
BlueZ development <linux-bluetooth@vger.kernel.org>,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 6lowpan: Allow 6LoWPAN to be modular
Date: Thu, 7 Aug 2014 09:00:36 -0700 [thread overview]
Message-ID: <ABE15994-F47B-4E4B-A6FC-79C6BCAC9FF3@holtmann.org> (raw)
In-Reply-To: <1407424003-15073-1-git-send-email-geert@linux-m68k.org>
Hi Geert,
> Change config symbol 6LOWPAN from type bool to type tristate, so
> 6LoWPAN can be built modular, just like IPV6
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> net/6lowpan/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/6lowpan/Kconfig b/net/6lowpan/Kconfig
> index 028a5c6d1f61..e4a02ef55102 100644
> --- a/net/6lowpan/Kconfig
> +++ b/net/6lowpan/Kconfig
> @@ -1,5 +1,5 @@
> config 6LOWPAN
> - bool "6LoWPAN Support"
> + tristate "6LoWPAN Support"
is this a regression from the previous CONFIG_6LOWPAN separation that we introduced? If it is, then it might be easiest if Dave just takes it into his net tree. Otherwise I take it through bluetooth-next.
Regards
Marcel
next prev parent reply other threads:[~2014-08-07 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 15:06 Geert Uytterhoeven
2014-08-07 16:00 ` Marcel Holtmann [this message]
2014-08-07 16:44 ` Geert Uytterhoeven
2014-08-07 18:31 ` Marcel Holtmann
2014-08-07 18:49 ` Alexander Aring
2014-08-07 19:05 ` 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=ABE15994-F47B-4E4B-A6FC-79C6BCAC9FF3@holtmann.org \
--to=marcel@holtmann.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®