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, yinghsu@chromium.org, 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: Free potentially unfreed SCO connection
Date: Fri, 03 Feb 2023 20:30:17 +0000 [thread overview]
Message-ID: <167545621774.19489.15945794650685892381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230203173024.1.Ieb6662276f3bd3d79e9134ab04523d584c300c45@changeid>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 3 Feb 2023 17:30:55 +0800 you wrote:
> From: Archie Pusaka <apusaka@chromium.org>
>
> It is possible to initiate a SCO connection while deleting the
> corresponding ACL connection, e.g. in below scenario:
>
> (1) < hci setup sync connect command
> (2) > hci disconn complete event (for the acl connection)
> (3) > hci command complete event (for(1), failure)
>
> [...]
Here is the summary with links:
- Bluetooth: Free potentially unfreed SCO connection
https://git.kernel.org/bluetooth/bluetooth-next/c/c2c762af5650
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-02-03 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 9:30 [PATCH] Bluetooth: Free potentially unfreed SCO connection Archie Pusaka
2023-02-03 9:57 ` bluez.test.bot
2023-02-03 20: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=167545621774.19489.15945794650685892381.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=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yinghsu@chromium.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.