From: patchwork-bot+bluetooth@kernel•org
To: Archie Pusaka <apusaka@google•com>
Cc: linux-bluetooth@vger•kernel.org, luiz.dentz@gmail•com,
marcel@holtmann•org, chromeos-bluetooth-upstreaming@chromium•org,
apusaka@chromium•org, abhishekpandit@google•com,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
johan.hedberg@gmail•com, pabeni@redhat•com,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [PATCH] Bluetooth: hci_sync: Don't wait peer's reply when powering off
Date: Tue, 07 Mar 2023 18:40:22 +0000 [thread overview]
Message-ID: <167821442261.6197.2161849719064064403.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230306170628.1.I8d0612b2968dd4740a4ceaf42f329fb59d5b9324@changeid>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel•com>:
On Mon, 6 Mar 2023 17:07:07 +0800 you wrote:
> From: Archie Pusaka <apusaka@chromium•org>
>
> Currently, when we initiate disconnection, we will wait for the peer's
> reply unless when we are suspending, where we fire and forget the
> disconnect request.
>
> A similar case is when adapter is powering off. However, we still wait
> for the peer's reply in this case. Therefore, if the peer is
> unresponsive, the command will time out and the power off sequence
> will fail, causing "bluetooth powered on by itself" to users.
>
> [...]
Here is the summary with links:
- Bluetooth: hci_sync: Don't wait peer's reply when powering off
https://git.kernel.org/bluetooth/bluetooth-next/c/bc044bb47d5a
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:[~2023-03-07 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 9:07 [PATCH] Bluetooth: hci_sync: Don't wait peer's reply when powering off Archie Pusaka
2023-03-06 12:44 ` Simon Horman
2023-03-07 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=167821442261.6197.2161849719064064403.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel$(echo .)org \
--cc=abhishekpandit@google$(echo .)com \
--cc=apusaka@chromium$(echo .)org \
--cc=apusaka@google$(echo .)com \
--cc=chromeos-bluetooth-upstreaming@chromium$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=luiz.dentz@gmail$(echo .)com \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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