From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 67d42a: monitor: Fix legacy SCAN_RSP PDU type names
Date: Fri, 02 Oct 2026 14:02:23 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1178588/000000-67d42a@github.com> (raw)
Branch: refs/heads/1178588
Home: https://github.com/bluez/bluez
Commit: 67d42a05a7e8c237e45e958bf5f702a955fe71a6
https://github.com/bluez/bluez/commit/67d42a05a7e8c237e45e958bf5f702a955fe71a6
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-02 (Fri, 02 Oct 2026)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: Fix legacy SCAN_RSP PDU type names
The names of the two legacy scan response event types are swapped. A
scan response keeps the properties of the advertisement it answers, so
0x1b, which has the connectable bit set, is the response to ADV_IND and
0x1a is the response to ADV_SCAN_IND, as listed in Core Specification
Vol 4, Part E, 7.7.65.13, Table 7.1.
Fixes: e29ef3b85116 ("monitor: Add LE Extended Scan commands decoding")
Assisted-by: Claude:claude-opus-5.5
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-02 21:02 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/1178588/000000-67d42a@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