From: patchwork-bot+bluetooth@kernel.org
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
Subject: Re: [Bluez PATCH v2 1/2] Monitor: Remove handle before assigning
Date: Tue, 30 Jan 2024 18:40:26 +0000 [thread overview]
Message-ID: <170664002653.26337.12062276527654167832.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240130182459.Bluez.v2.1.If74ccbca4d541c5f576765a3a78cb8923b5f85b1@changeid>
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
prev parent reply other threads:[~2024-01-30 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 10:24 [Bluez PATCH v2 1/2] Monitor: Remove handle before assigning Archie Pusaka
2024-01-30 10:25 ` [Bluez PATCH v2 2/2] Monitor: Avoid printing stale address on connection event Archie Pusaka
2024-01-30 11:42 ` [Bluez,v2,1/2] Monitor: Remove handle before assigning bluez.test.bot
2024-01-30 18:40 ` patchwork-bot+bluetooth [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=170664002653.26337.12062276527654167832.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=apusaka@chromium.org \
--cc=apusaka@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=jiangzp@google.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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).