From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] client/btpclient: Fix GAP unpair command
Date: Tue, 02 Jun 2026 17:30:05 +0000 [thread overview]
Message-ID: <178042140556.969144.3241776766056523976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260519085016.188744-1-frederic.danis@collabora.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 19 May 2026 10:50:15 +0200 you wrote:
> Fix unpair_reply() because the device is no more available on
> RemoveDevice reply.
> ---
> client/btpclient/gap.c | 40 +++++++++++++++++++++++-----------------
> 1 file changed, 23 insertions(+), 17 deletions(-)
Here is the summary with links:
- [BlueZ,v2,1/2] client/btpclient: Fix GAP unpair command
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=96a51d53ccf3
- [BlueZ,v2,2/2] client/btpclient: Don't remove all devices on GAP Reset command
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=07b6fc156348
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:[~2026-06-02 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 8:50 [PATCH BlueZ v2 1/2] client/btpclient: Fix GAP unpair command Frédéric Danis
2026-05-19 8:50 ` [PATCH BlueZ v2 2/2] client/btpclient: Don't remove all devices on GAP Reset command Frédéric Danis
2026-05-19 12:23 ` [BlueZ,v2,1/2] client/btpclient: Fix GAP unpair command bluez.test.bot
2026-06-02 17:30 ` 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=178042140556.969144.3241776766056523976.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--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