From: Dimitris <dimitris.on.linux@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Dimitris <dimitris.on.linux@gmail.com>
Subject: [PATCH BlueZ 0/1] Fixes busy loop when disabling
Date: Wed, 3 Apr 2024 13:52:51 -0700 [thread overview]
Message-ID: <20240403205252.71978-1-dimitris.on.linux@gmail.com> (raw)
Reverts a commit which causes bluetoothd to enter a busy loop if
BT is disabled (eg. rfkill block bluetooth) when one or more
devices are connected.
Steps to reproduce are described in these reports:
https://github.com/bluez/bluez/issues/785
https://bugzilla.redhat.com/show_bug.cgi?id=2269516
Dimitris (1):
Revert "device: Consider service state on device_is_connected"
src/device.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-03 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 20:52 Dimitris [this message]
2024-04-03 20:52 ` [PATCH BlueZ 1/1] Revert "device: Consider service state on device_is_connected" Dimitris
2024-04-03 22:39 ` Fixes busy loop when disabling bluez.test.bot
2024-04-04 6:24 ` [PATCH BlueZ 1/1] Revert "device: Consider service state on device_is_connected" Paul Menzel
2024-04-04 6:35 ` Dimitris
2024-04-04 2:45 ` [PATCH BlueZ 0/1] V2: Fix busy loop when disabling BT Dimitris
2024-04-04 2:45 ` [PATCH BlueZ 1/1] Refactor btd_device_is_connected Dimitris
2024-04-04 4:40 ` V2: Fix busy loop when disabling BT bluez.test.bot
2024-04-04 14:59 ` [PATCH BlueZ 1/1] Refactor btd_device_is_connected Luiz Augusto von Dentz
2024-04-04 15:52 ` Dimitris
2024-04-04 16:16 ` Luiz Augusto von Dentz
2024-04-04 18:25 ` Dimitris
2024-04-04 18:30 ` [PATCH BlueZ 0/1] V3: Fix busy loop when disabling BT Dimitris
2024-04-04 18:30 ` [PATCH BlueZ 1/1] refactor bearer connected test Dimitris
2024-04-04 20:07 ` V3: Fix busy loop when disabling BT bluez.test.bot
2024-04-04 18:50 ` [PATCH BlueZ 0/1] " patchwork-bot+bluetooth
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=20240403205252.71978-1-dimitris.on.linux@gmail.com \
--to=dimitris.on.linux@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.