From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 81bb03: doc/hci-protocol: Fix missing & on mtu argument in...
Date: Mon, 31 Aug 2026 00:12:32 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1154126/000000-ed22f8@github.com> (raw)
Branch: refs/heads/1154126
Home: https://github.com/bluez/bluez
Commit: 81bb0309c998ea821502c04bc47c26a4b12b843e
https://github.com/bluez/bluez/commit/81bb0309c998ea821502c04bc47c26a4b12b843e
Author: Zijun Hu <zijun.hu@oss.qualcomm.com>
Date: 2026-08-31 (Mon, 31 Aug 2026)
Changed paths:
M doc/hci-protocol.rst
Log Message:
-----------
doc/hci-protocol: Fix missing & on mtu argument in BT_RCVMTU example
getsockopt() requires a pointer argument, but mtu was passed by value.
Fix by using &mtu instead of mtu.
Commit: d51fbc57419250ce832cf9ed7f3fc5e43ca3eb0e
https://github.com/bluez/bluez/commit/d51fbc57419250ce832cf9ed7f3fc5e43ca3eb0e
Author: Zijun Hu <zijun.hu@oss.qualcomm.com>
Date: 2026-08-31 (Mon, 31 Aug 2026)
Changed paths:
M doc/hci-protocol.rst
Log Message:
-----------
doc/hci-protocol: Add BT_RECV_VENDOR_PKT socket option for HCI_CHANNEL_USER
BT_RECV_VENDOR_PKT controls receiving vendor HCI packets over
HCI_CHANNEL_USER.
Disabled by default to avoid regressions for existing applications.
Commit: ed22f8b615f07cbc13d0a35f440be628c0cf6c72
https://github.com/bluez/bluez/commit/ed22f8b615f07cbc13d0a35f440be628c0cf6c72
Author: Zijun Hu <zijun.hu@oss.qualcomm.com>
Date: 2026-08-31 (Mon, 31 Aug 2026)
Changed paths:
M doc/btsnoop-protocol.rst
M monitor/analyze.c
M monitor/packet.c
M monitor/packet.h
M src/shared/btsnoop.h
Log Message:
-----------
monitor: Support vendor HCI packets
Vendor HCI packets have 0xff as packet type.
Support them in tool btmon.
Compare: https://github.com/bluez/bluez/compare/81bb0309c998%5E...ed22f8b615f0
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-31 7:12 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/1154126/000000-ed22f8@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.