Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: [PATCH v3 0/3] bluetooth: 6lowpan: multiple peers and addresses
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <20190706155448.13382-1-josua.mayer@jm0.eu>
Date:   Sat, 6 Jul 2019 21:44:48 +0200
Cc:     linux-bluetooth@vger.kernel.org
Content-Transfer-Encoding: 7bit
Message-Id: <5A501DEB-B2CA-4C3B-AF5E-F2E5816AA5D0@holtmann.org>
References: <20190706155448.13382-1-josua.mayer@jm0.eu>
To:     Josua Mayer <josua.mayer@jm0.eu>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Josua,

> This patch set deals with an issue I reported earlier this year, where
> 1) packets addressed to a non-link-local address
> 2) any packets when at least 2 peers are connected
> were not delivered if they matched a direct peer i.e. no routing.
> 
> The full explanation of the issue including steps to reproduce are:
> https://www.spinics.net/lists/linux-bluetooth/msg78486.html
> 
> Changes since v2:
> - rebased on bluetooth-next
> 
> Changes since v1:
> - changed comment style to c++
> 
> Josua Mayer (3):
> bluetooth: 6lowpan: search for destination address in all peers
> bluetooth: 6lowpan: check neighbour table for SLAAC
> bluetooth: 6lowpan: always check destination address
> 
> net/bluetooth/6lowpan.c | 41 +++++++++++++++++++++++++----------------
> 1 file changed, 25 insertions(+), 16 deletions(-)

all 3 patches have been applied to bluetooth-next tree.

Regards

Marcel