Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-1494-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [Bluez PATCH v2 1/2] Monitor: Remove handle before assigning
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170664002653.26337.12062276527654167832.git-patchwork-notify@kernel.org>
Date: Tue, 30 Jan 2024 18:40:26 +0000
References: <20240130182459.Bluez.v2.1.If74ccbca4d541c5f576765a3a78cb8923b5f85b1@changeid>
In-Reply-To: <20240130182459.Bluez.v2.1.If74ccbca4d541c5f576765a3a78cb8923b5f85b1@changeid>
To: Archie Pusaka <apusaka@google.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
 johan.hedberg@gmail.com, marcel@holtmann.org,
 chromeos-bluetooth-upstreaming@chromium.org, apusaka@chromium.org,
 jiangzp@google.com

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 30 Jan 2024 18:24:59 +0800 you wrote:
> From: Archie Pusaka <apusaka@chromium.org>
> 
> It is possible to have some handles not removed, for example the host
> may decide not to wait for disconnection complete event when it is
> suspending. In this case, when the peer device reconnected, we might
> have two of the some handle assigned and create problem down the road.
> 
> [...]

Here is the summary with links:
  - [Bluez,v2,1/2] Monitor: Remove handle before assigning
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=12ccf5ea0fa5
  - [Bluez,v2,2/2] Monitor: Avoid printing stale address on connection event
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e98bbe3f1cb2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html