Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kyle Pepper <cochcoder@proton.me>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	luiz.von.dentz@gmail.com
Subject: Re: [PATCH v2] shared/asha: prime volume before starting audio
Date: Tue, 10 Nov 2026 22:00:07 +0000	[thread overview]
Message-ID: <179434800767.80411.13470774413251516410.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261107010019.1162372-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:01:13 +0000 you wrote:
> Prime the Volume characteristic with the cached volume before START so
> both volume inputs are initialized when audio starts. Keep the write
> best effort so a rejected volume write does not prevent START.
> 
> Assisted-by: OpenCode:gpt-6.1-sol
> Assisted-by: Codex:gpt-6
> 
> [...]

Here is the summary with links:
  - [v2] shared/asha: prime volume before starting audio
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4287b3addc20

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-10 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 13:31 [PATCH RESEND] shared/asha: prime volume before starting audio Kyle Pepper
2026-10-28 16:25 ` [RESEND] " bluez.test.bot
2026-11-07  1:01 ` [PATCH v2] " Kyle Pepper
2026-11-07  2:51   ` [v2] " bluez.test.bot
2026-11-07  7:02   ` [PATCH v2] " cochcoder
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=179434800767.80411.13470774413251516410.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=cochcoder@proton.me \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.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