From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 6939c4: btdev: Add le_big on BT_HCI_CMD_LE_CREATE_BIG
Date: Fri, 25 Jul 2025 06:50:26 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/da772d-00ffc5@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 6939c4706c908541278aab9ddad5624f2c32744d
https://github.com/bluez/bluez/commit/6939c4706c908541278aab9ddad5624f2c32744d
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-25 (Fri, 25 Jul 2025)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
btdev: Add le_big on BT_HCI_CMD_LE_CREATE_BIG
When handling BT_HCI_CMD_LE_CREATE_BIG create a struct le_big to
represent it otherwise the likes of BT_HCI_CMD_LE_TERM_BIG will not be
able to detect a BIG was created.
Commit: d427a2a5f1977f1620dc9128863ad0d64d056ccb
https://github.com/bluez/bluez/commit/d427a2a5f1977f1620dc9128863ad0d64d056ccb
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-25 (Fri, 25 Jul 2025)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
btdev: Fix handling of BT_HCI_CMD_LE_TERM_BIG
BT_HCI_CMD_LE_TERM_BIG shall cleanup the BIS connections and if there
are remote connected then they shall be notified with
BT_HCI_EVT_LE_BIG_SYNC_LOST so they can proceed to cleanup as well.
Commit: 00ffc553a194c2ca1db52dacd42838a135b4ef65
https://github.com/bluez/bluez/commit/00ffc553a194c2ca1db52dacd42838a135b4ef65
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-25 (Fri, 25 Jul 2025)
Changed paths:
M btio/btio.c
Log Message:
-----------
btio: Fix handling of getpeername
getpeername can either return an error set in the errno or the
returned size can be invalid but in that case errno is not set so
printing it would generate bogus message.
Compare: https://github.com/bluez/bluez/compare/da772d62b295...00ffc553a194
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-25 13:50 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/da772d-00ffc5@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