From: patchwork-bot+bluetooth@kernel.org
To: Kyle Pepper <cochcoder@proton.me>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ v2] shared/asha: Send STOP without a response
Date: Tue, 10 Nov 2026 22:00:09 +0000 [thread overview]
Message-ID: <179434800919.80411.704170822998959847.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261107012310.1224254-1-cochcoder@proton.me>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 07 Nov 2026 01:24:00 +0000 you wrote:
> Avoid leaving a STOP Write Request pending after local state has been
> reset. Send a Write Command using the existing helper instead.
>
> ASHA specifies Write with response for STOP; this changes that procedure
> and needs renderer STOP/restart validation.
>
> Fixes: 9948168cca15 ("shared/asha: Don't wait for status notification on stop")
> Assisted-by: OpenCode:gpt-6.1-sol
> Assisted-by: Codex:gpt-6
>
> [...]
Here is the summary with links:
- [BlueZ,v2] shared/asha: Send STOP without a response
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d3e258ce4d0a
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-11-10 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 13:30 [PATCH RESEND] shared/asha: send STOP without waiting for a response Kyle Pepper
2026-10-28 16:02 ` [RESEND] " bluez.test.bot
2026-11-07 1:24 ` [PATCH BlueZ v2] shared/asha: Send STOP without " Kyle Pepper
2026-11-07 2:52 ` [BlueZ,v2] " bluez.test.bot
2026-11-10 22:00 ` 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=179434800919.80411.704170822998959847.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=cochcoder@proton.me \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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