From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 322c39: bap: Start BIG sync after receiving BIGInfo
Date: Tue, 28 Jul 2026 08:29:19 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/89d477-729f96@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 322c39a643232643ccd514a8f8dfc9683e3e3f1b
https://github.com/bluez/bluez/commit/322c39a643232643ccd514a8f8dfc9683e3e3f1b
Author: Yang Li <yang.li@amlogic.com>
Date: 2026-07-27 (Mon, 27 Jul 2026)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Start BIG sync after receiving BIGInfo
The current implementation starts BIG sync before receiving a BIGInfo
report. According to the Bluetooth Core Specification, BIG sync should
only be initiated after BIGInfo has been received.
Starting BIG sync too early may cause unexpected controller behavior.
Trigger BIG sync from the BIGInfo callback, following the same approach
used by the short PA flow.
Fixes: https://github.com/bluez/bluez/issues/2345
Commit: 729f96089cf66831d911385623ca932e0c245913
https://github.com/bluez/bluez/commit/729f96089cf66831d911385623ca932e0c245913
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-07-27 (Mon, 27 Jul 2026)
Changed paths:
M .github/workflows/stale.yml
Log Message:
-----------
github: Disable stale bot for triaged bugs
When the "bug" label is set on an issue, don't reap it with the stale
bot, as we've triaged the problem and seen a bug.
Compare: https://github.com/bluez/bluez/compare/89d477bb5494...729f96089cf6
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-28 15:29 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/89d477-729f96@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 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.