All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"bluez mailin list (linux-bluetooth@vger.kernel.org)"
	<linux-bluetooth@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH bluetooth-next] bluetooth: make bluetooth 6lowpan as an option
Date: Tue, 11 Mar 2014 19:20:01 +0100	[thread overview]
Message-ID: <20140311182000.GA11022@omega> (raw)
In-Reply-To: <5D79FB52-77AC-4391-9CAB-6F792388EFD8@holtmann.org>

Hi Marcel,

On Tue, Mar 11, 2014 at 07:56:52AM -0700, Marcel Holtmann wrote:
> Hi Alexander,
> 
> > Currently you can have bluetooth 6lowpan without ipv6 enabled. This
> > doesn't make any sense. With this patch you can disable/enable bluetooth
> > 6lowpan support at compile time.
> > 
> > The current bluetooth 6lowpan implementation doesn't check the return
> > value of 6lowpan function. Nevertheless I added -EOPNOTSUPP as return value
> > if 6lowpan bluetooth is disabled.
> > 
> > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > ---
> > net/bluetooth/6lowpan.h | 21 +++++++++++++++++++++
> > net/bluetooth/Kconfig   |  8 +++++++-
> > net/bluetooth/Makefile  |  3 ++-
> > 3 files changed, 30 insertions(+), 2 deletions(-)
> 
> patch has been applied to bluetooth-next tree.
> 

thanks and I see that next time I need to write:

"Bluetooth: ..." instead "bluetooth: ..."

Sorry, about that!

- Alex

      reply	other threads:[~2014-03-11 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  9:23 [PATCH bluetooth-next] bluetooth: make bluetooth 6lowpan as an option Alexander Aring
2014-03-04  9:23 ` Alexander Aring
2014-03-11 14:56 ` Marcel Holtmann
2014-03-11 18:20   ` Alexander Aring [this message]

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=20140311182000.GA11022@omega \
    --to=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --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 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.