All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] transport: fix A2DP Delay values missing from DBus
Date: Mon, 18 Aug 2025 21:40:05 +0000	[thread overview]
Message-ID: <175555320551.2921497.4085203346902965611.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b2fba95d658c75135f0ee7b4bc11e193be126622.1755334561.git.pav@iki.fi>

Hello:

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

On Sat, 16 Aug 2025 11:56:53 +0300 you wrote:
> With headsets, a2dp_transport::session == NULL usually until stream
> resumes. During this time, delay_reporting_exists() incorrectly returns
> FALSE, because streams corresponding to NULL session cannot be found.
> As no further "Delay" property updates will usually arrive, the property
> remains missing even though delay reports have been received.
> 
> Fix by setting a2dp->session when processing a delay report, if missing.
> 
> [...]

Here is the summary with links:
  - [BlueZ] transport: fix A2DP Delay values missing from DBus
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0bb66d3d1abd

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-18 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16  8:56 [PATCH BlueZ] transport: fix A2DP Delay values missing from DBus Pauli Virtanen
2025-08-16 10:27 ` [BlueZ] " bluez.test.bot
2025-08-18 21:40 ` 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=175555320551.2921497.4085203346902965611.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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.