linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrik Flykt <patrik.flykt@linux.intel.com>
To: linux-bluetooth@vger.kernel.org, aar@pengutronix.de,
	jukka.rissanen@linux.intel.com
Subject: [RFC 4/4] bluetooth: Do not set IFF_POINTOPOINT
Date: Mon, 20 Jun 2016 10:49:53 +0300	[thread overview]
Message-ID: <1466408993-3808-5-git-send-email-patrik.flykt@linux.intel.com> (raw)
In-Reply-To: <1466408993-3808-1-git-send-email-patrik.flykt@linux.intel.com>

The IPv6 stack needs to send and receive Neighbor Discovery
messages. Remove the IFF_POINTOPOINT flag.

Signed-off-by: Patrik Flykt <patrik.flykt@linux.intel.com>
---
 net/bluetooth/6lowpan.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/net/bluetooth/6lowpan.c b/net/bluetooth/6lowpan.c
index 2dddb2b..1a70312 100644
--- a/net/bluetooth/6lowpan.c
+++ b/net/bluetooth/6lowpan.c
@@ -650,8 +650,7 @@ static void netdev_setup(struct net_device *dev)
 {
 	dev->hard_header_len	= 0;
 	dev->needed_tailroom	= 0;
-	dev->flags		= IFF_RUNNING | IFF_POINTOPOINT |
-				  IFF_MULTICAST;
+	dev->flags		= IFF_RUNNING | IFF_MULTICAST;
 	dev->watchdog_timeo	= 0;
 
 	dev->netdev_ops		= &netdev_ops;
-- 
2.8.1


  parent reply	other threads:[~2016-06-20  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20  7:49 [RFC 0/4] Fix BT 6lowpan point-to-point interface Patrik Flykt
2016-06-20  7:49 ` [RFC 1/4] addrconf: Create EUI48 IPv6 addresses for BTLE 6LoWPAN Patrik Flykt
2016-11-22 12:26   ` Luiz Augusto von Dentz
2016-11-22 15:28     ` Alexander Aring
2016-06-20  7:49 ` [RFC 2/4] 6lowpan: Set MAC address lenght according to LOWPAN_LLTYPE Patrik Flykt
2016-06-20 10:46   ` Alexander Aring
2016-06-20 11:18   ` Alexander Aring
2016-06-20  7:49 ` [RFC 3/4] bluetooth: Set 6 byte device addresses Patrik Flykt
2016-06-20 11:08   ` Alexander Aring
2016-06-20  7:49 ` Patrik Flykt [this message]
2016-06-20 12:56   ` [RFC 4/4] bluetooth: Do not set IFF_POINTOPOINT Luiz Augusto von Dentz

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=1466408993-3808-5-git-send-email-patrik.flykt@linux.intel.com \
    --to=patrik.flykt@linux.intel.com \
    --cc=aar@pengutronix.de \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@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).