From: patchwork-bot+bluetooth@kernel.org
To: Youwan Wang <wangyouwan@uniontech.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] device: Fix not removing connected device
Date: Thu, 23 Jun 2022 23:30:13 +0000 [thread overview]
Message-ID: <165602701399.3875.5236197071224398310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220623062953.13419-1-wangyouwan@uniontech.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 23 Jun 2022 14:29:53 +0800 you wrote:
> [bluetooth]# connect 40:EF:4C:0C:11:F0
> Attempting to connect to 40:EF:4C:0C:11:F0
> [CHG] Device 40:EF:4C:0C:11:F0 Connected: yes
> Connection successful
> [CHG] Device 40:EF:4C:0C:11:F0 ServicesResolved: yes
> [UFO]# remove 40:EF:4C:0C:11:F0
> [CHG] Device 40:EF:4C:0C:11:F0 ServicesResolved: no
> Device has been removed
> [CHG] Device 40:EF:4C:0C:11:F0 Connected: no
> [bluetooth]# info 40:EF:4C:0C:11:F0
> Device 40:EF:4C:0C:11:F0 (public)
> Name: UFO
> Alias: UFO
> Class: 0x00240418
> Icon: audio-headphones
> Paired: yes
> Trusted: no
> Blocked: no
> Connected: no
> LegacyPairing: no
> UUID: Headset
> UUID: Audio Sink
> UUID: A/V Remote Control Target
> UUID: A/V Remote Control
> UUID: Handsfree
> UUID: Phonebook Access Server
>
> [...]
Here is the summary with links:
- device: Fix not removing connected device
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=65f7faf5a3d0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-06-23 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 6:29 [PATCH] device: Fix not removing connected device Youwan Wang
2022-06-23 8:08 ` bluez.test.bot
2022-06-23 23:30 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 3:13 [PATCH] " Youwan Wang
2022-06-23 1:44 Youwan Wang
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=165602701399.3875.5236197071224398310.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wangyouwan@uniontech.com \
/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).