From: patchwork-bot+bluetooth@kernel.org
To: Myrrh Periwinkle <myrrhperiwinkle@qtmlabs.xyz>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: Re: [PATCH bluez v4 0/2] audio: Don't initialize media transport volume from media player
Date: Tue, 12 Aug 2025 18:10:06 +0000 [thread overview]
Message-ID: <175502220698.2767383.8444233719893678441.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250806-audio-no-reuse-media-player-volume-v4-0-a59d9a4848c1@qtmlabs.xyz>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 06 Aug 2025 09:22:45 +0700 you wrote:
> Fixes an issue where if a Bluetooth headphone with hardware volume
> control was connected while mpris-proxy was running, disconnected and
> replaced with a different one without hardware volume control, the
> latter will be erroneously recognized as hardware volume
> control capable.
>
>
> [...]
Here is the summary with links:
- [bluez,v4,1/2] audio: Don't initialize media transport volume from media player
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5db6d2fef66f
- [bluez,v4,2/2] audio: Remove media_player.volume
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9cdbad590b74
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:[~2025-08-12 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 2:22 [PATCH bluez v4 0/2] audio: Don't initialize media transport volume from media player Myrrh Periwinkle
2025-08-06 2:22 ` [PATCH bluez v4 1/2] " Myrrh Periwinkle
2025-08-06 4:32 ` bluez.test.bot
2025-08-06 2:22 ` [PATCH bluez v4 2/2] audio: Remove media_player.volume Myrrh Periwinkle
2025-08-12 18:10 ` 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=175502220698.2767383.8444233719893678441.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=myrrhperiwinkle@qtmlabs.xyz \
/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