From: patchwork-bot+bluetooth@kernel.org
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
bartosz@fabianowski.eu
Subject: Re: [PATCH BlueZ] audio/transport: Propagate errors from avrcp_set_volume to DBus
Date: Tue, 21 Mar 2023 16:00:17 +0000 [thread overview]
Message-ID: <167941441794.2626.8050550544503930436.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230311011202.486271-1-marijn.suijten@somainline.org>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 11 Mar 2023 02:12:02 +0100 you wrote:
> Any error while setting absolute volume on the peer, or notifying the
> peer of changes was previously going completely unnoticed. Propagate it
> to the logs and back to the DBus "Volume" property setter so that they
> aren't misled into thinking that the AVRCP command succeeded.
>
> Note that an error is mostly harmless when the setter of the property is
> an audio sink and the peer the audio source: in this case we're only
> _notifying_ the peer of the change when it has already been applied on
> the sink.
>
> [...]
Here is the summary with links:
- [BlueZ] audio/transport: Propagate errors from avrcp_set_volume to DBus
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1de41786c1a2
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-03-21 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 1:12 [PATCH BlueZ] audio/transport: Propagate errors from avrcp_set_volume to DBus Marijn Suijten
2023-03-11 3:34 ` [BlueZ] " bluez.test.bot
2023-03-21 16: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=167941441794.2626.8050550544503930436.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bartosz@fabianowski.eu \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marijn.suijten@somainline.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