From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] da5846: dbus: Fix condition for invalidating path
Date: Tue, 01 Apr 2025 14:13:38 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/47e5d3-6d20a3@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: da5846c096cd1006d512bbdbc466fc46a61417b8
https://github.com/bluez/bluez/commit/da5846c096cd1006d512bbdbc466fc46a61417b8
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-04-01 (Tue, 01 Apr 2025)
Changed paths:
M gdbus/object.c
Log Message:
-----------
dbus: Fix condition for invalidating path
This fixes the condition introduced in cdd02afbb7ef
("dbus: Fix add invalid memory during interface removal") which was
reversed while applying the original fix.
Fixes: https://github.com/bluez/bluez/issues/1155
Commit: 6d20a300642f312290af0bc9869a0e1b416c58dc
https://github.com/bluez/bluez/commit/6d20a300642f312290af0bc9869a0e1b416c58dc
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-04-01 (Tue, 01 Apr 2025)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Fix swallowing states transitions
In certain cases (e.g ASCS_Enable) a Control Point operation may change
states multiple times causing states not to be notified.
To fix this attempts to queue states if timeout is pending (state_id)
and then proceed to notify them ahead of the last state set in the ASE
so the remote side is informed of all the state transitions.
Compare: https://github.com/bluez/bluez/compare/47e5d3491d37...6d20a300642f
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-04-01 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/47e5d3-6d20a3@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.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