From: "Łukasz Rymanowski" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 4337eb: monitor: Fix adv_handle size in the set info trans...
Date: Fri, 21 Jul 2023 13:31:17 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/82d3d8-d8ca06@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 4337eb25b04cc168a102c56e817fef20bb62cf75
https://github.com/bluez/bluez/commit/4337eb25b04cc168a102c56e817fef20bb62cf75
Author: Jakub Tyszkowski <jakub.tyszkowski@codecoup.pl>
Date: 2023-07-21 (Fri, 21 Jul 2023)
Changed paths:
M monitor/bt.h
Log Message:
-----------
monitor: Fix adv_handle size in the set info transfer packet
As per Bluetooth Core 5.4 Vol 4. Part E, 7.8.90,
adv_handle is 1 octet size and not 2.
Commit: cc9f3a8e510a5ac8c0441a7714256dca969b695b
https://github.com/bluez/bluez/commit/cc9f3a8e510a5ac8c0441a7714256dca969b695b
Author: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@codecoup.pl>
Date: 2023-07-21 (Fri, 21 Jul 2023)
Changed paths:
M monitor/bt.h
Log Message:
-----------
monitor: Fix invalid Create BIG Test command
As per Bluetooth Core 5.4 Vol 4 Part E, 7.8.104,
max pdu is 2 octect long and there is no adv_handle before encyption
flag
Commit: aee361c8eb0fd0fa102ed4190de526cc339b8906
https://github.com/bluez/bluez/commit/aee361c8eb0fd0fa102ed4190de526cc339b8906
Author: Łukasz Rymanowski <lukasz.rymanowski@codecoup.pl>
Date: 2023-07-21 (Fri, 21 Jul 2023)
Changed paths:
M monitor/packet.c
Log Message:
-----------
btmon: Fix obvious typo
Commit: d8ca06631b7434ea8837f9c571bfe31d6602d31f
https://github.com/bluez/bluez/commit/d8ca06631b7434ea8837f9c571bfe31d6602d31f
Author: Łukasz Rymanowski <lukasz.rymanowski@codecoup.pl>
Date: 2023-07-21 (Fri, 21 Jul 2023)
Changed paths:
M monitor/bt.h
M monitor/packet.c
Log Message:
-----------
btmon: Make BIG identifier consistent
Bluetooth spec uses BIG Handle as a BIG identifier.
Btmon sometimes use this and sometimes BIG ID.
This patch makes code consistent
Compare: https://github.com/bluez/bluez/compare/82d3d803d4c5...d8ca06631b74
reply other threads:[~2023-07-21 20:31 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/82d3d8-d8ca06@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.