From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5b684c: emulator: Remove unused le_ext_adv_type
Date: Mon, 05 Oct 2026 12:14:04 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1179769/000000-d83398@github.com> (raw)
Branch: refs/heads/1179769
Home: https://github.com/bluez/bluez
Commit: 5b684c04681ee0ddbfd5d46a38129b5930080a87
https://github.com/bluez/bluez/commit/5b684c04681ee0ddbfd5d46a38129b5930080a87
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-05 (Mon, 05 Oct 2026)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
emulator: Remove unused le_ext_adv_type
Nothing has read le_ext_adv_type since advertising sets got their own
struct le_ext_adv in commit 5145b1ea2e95 ("emulator/btdev: Add support
multiple instance of extended advertising"). Remove it along with
ext_legacy_adv_type, rather than fix that function's mapping of low
duty cycle directed advertising (0x04) to ADV_SCAN_IND.
Assisted-by: Claude:claude-opus-5.5
Commit: 140f8097918b6e7e770ae64c3531488074e7ff4d
https://github.com/bluez/bluez/commit/140f8097918b6e7e770ae64c3531488074e7ff4d
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-05 (Mon, 05 Oct 2026)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
emulator: Fix extended scan response Event_Type
The scan response to non-legacy scannable advertising was reported with
Event_Type 0x0000, since the scan response bit was masked instead of
set, so hosts saw it as a separate non-connectable advertisement.
Fixes: 32339501a125 ("emulator: Add 5.0 feature support")
Assisted-by: Claude:claude-opus-5.5
Commit: d83398e628fa2c76cca7cb0db0811e27ab7b963a
https://github.com/bluez/bluez/commit/d83398e628fa2c76cca7cb0db0811e27ab7b963a
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-05 (Mon, 05 Oct 2026)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
emulator: Fix report type after a scan response
ext_adv_broadcast stored the scan response type in report_type, which
is also used for the advertising report to the next scanner, so every
active scanner after the first got the advertisement reported as a scan
response.
Fixes: 32339501a125 ("emulator: Add 5.0 feature support")
Assisted-by: Claude:claude-opus-5.5
Compare: https://github.com/bluez/bluez/compare/5b684c04681e%5E...d83398e628fa
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-05 19:14 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/1179769/000000-d83398@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