All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Myrrh Periwinkle <myrrhperiwinkle@qtmlabs.xyz>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH bluez] audio: Don't initialize device volume from media player
Date: Tue, 12 Aug 2025 18:10:05 +0000	[thread overview]
Message-ID: <175502220575.2767383.5429223419974091860.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250805-audio-no-reuse-media-player-volume-v1-1-c9fdfaf74a71@qtmlabs.xyz>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 05 Aug 2025 17:21:28 +0700 you wrote:
> Media player objects may be shared between devices. As a result,
> a device without support for hardware volume that is connected after one
> that does may end up being erroneously considered hardware
> volume-capable.
> 
> fa7828bdd ("transport: Fix not being able to initialize volume properly")
> introduced btd_device_{get,set}_volume that is used as an alternative in
> case no media player objects are present. Therefore, we can remove
> media_player_get_device_volume and instead use btd_device_get_volume to
> determine the initial volume.
> 
> [...]

Here is the summary with links:
  - [bluez] audio: Don't initialize device volume from media player
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5db6d2fef66f

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



      parent reply	other threads:[~2025-08-12 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 10:21 [PATCH bluez] audio: Don't initialize device volume from media player Myrrh Periwinkle
2025-08-05 12:02 ` [bluez] " bluez.test.bot
2025-08-05 15:24 ` [PATCH bluez] " Luiz Augusto von Dentz
2025-08-05 15:34   ` Myrrh Periwinkle
2025-08-05 16:01     ` Luiz Augusto von Dentz
2025-08-05 16:08       ` Myrrh Periwinkle
2025-08-06  0:50         ` 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=175502220575.2767383.5429223419974091860.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --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 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.