linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: netdev@vger.kernel.org, jukka.rissanen@linux.intel.com,
	linux-zigbee-devel@lists.sourceforge.net,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] 6lowpan: introduce new net/6lowpan directory
Date: Fri, 11 Jul 2014 13:35:10 +0200	[thread overview]
Message-ID: <20140711113507.GA24370@omega> (raw)
In-Reply-To: <8A1EF84C-3EDC-4540-B8F4-1FCBF4BF8D93@holtmann.org>

Hi Marcel,

On Fri, Jul 11, 2014 at 01:23:52PM +0200, Marcel Holtmann wrote:
> Hi Alexander,
> 
...
> > index cbbbe6d..7ed1970 100644
> > --- a/net/Makefile
> > +++ b/net/Makefile
> > @@ -57,7 +57,8 @@ obj-$(CONFIG_CAIF)		+= caif/
> > ifneq ($(CONFIG_DCB),)
> > obj-y				+= dcb/
> > endif
> > -obj-y				+= ieee802154/
> > +obj-$(CONFIG_6LOWPAN)		+= 6lowpan/
> > +obj-$(CONFIG_IEEE802154)	+= ieee802154/
> > obj-$(CONFIG_MAC802154)		+= mac802154/
> > 
> > ifeq ($(CONFIG_NET),y)
> > diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig
> > index 06ec144..a54777d 100644
> > --- a/net/bluetooth/Kconfig
> > +++ b/net/bluetooth/Kconfig
> > @@ -6,7 +6,6 @@ menuconfig BT
> > 	tristate "Bluetooth subsystem support"
> > 	depends on NET && !S390
> > 	depends on RFKILL || !RFKILL
> > -	select 6LOWPAN_IPHC if BT_6LOWPAN
> > 	select CRC16
> > 	select CRYPTO
> > 	select CRYPTO_BLKCIPHER
> > @@ -42,7 +41,7 @@ menuconfig BT
> > 
> > config BT_6LOWPAN
> > 	bool "Bluetooth 6LoWPAN support"
> > -	depends on BT && IPV6
> > +	depends on BT && 6LOWPAN
> > 	help
> > 	  IPv6 compression over Bluetooth.
> 
> this will conflict with our changes in wireless-next tree. We converted out 6LoWPAN support into a separate module.
> 

oops, sorry I didn't check on this. I simple based it on net-next,
because the patch series adds a new branch.



btw. we need to talk about who branch will commit changes to iphc code
to avoid conflicts.

- Alex

  reply	other threads:[~2014-07-11 11:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  8:24 [PATCH net-next 0/2] Introduce generic 6LoWPAN branch Alexander Aring
2014-07-11  8:24 ` [PATCH net-next 1/2] 6lowpan: introduce new net/6lowpan directory Alexander Aring
2014-07-11 11:23   ` Marcel Holtmann
2014-07-11 11:35     ` Alexander Aring [this message]
2014-07-11 12:33       ` Marcel Holtmann
2014-07-11 18:54         ` David Miller
2014-07-11 22:54         ` Alexander Aring
2014-07-11 23:58           ` Marcel Holtmann
2014-07-12  9:17             ` Alexander Aring
2014-07-12  9:42               ` Marcel Holtmann
2014-07-11  8:24 ` [PATCH net-next 2/2] MAINTAINERS: add net/6lowpan/ maintainer entry Alexander Aring
2014-07-11 11:24   ` Marcel Holtmann
2014-07-11  9:57 ` [Linux-zigbee-devel] [PATCH net-next 0/2] Introduce generic 6LoWPAN branch Varka Bhadram
2014-07-11 10:25 ` Jukka Rissanen

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=20140711113507.GA24370@omega \
    --to=alex.aring@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --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;
as well as URLs for NNTP newsgroup(s).