From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e7eb72: doc: hci-protocol: Correct mtu to &mtu for getsock...
Date: Mon, 20 Jul 2026 00:47:08 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1130548/000000-0108e6@github.com> (raw)
Branch: refs/heads/1130548
Home: https://github.com/bluez/bluez
Commit: e7eb72a78a583092ea1ef189e56a8d6c6f968d22
https://github.com/bluez/bluez/commit/e7eb72a78a583092ea1ef189e56a8d6c6f968d22
Author: Zijun Hu <zijun.hu@oss.qualcomm.com>
Date: 2026-07-20 (Mon, 20 Jul 2026)
Changed paths:
M doc/hci-protocol.rst
Log Message:
-----------
doc: hci-protocol: Correct mtu to &mtu for getsockopt BT_RCVMTU
For getsockopt(..., BT_RCVMTU, ...):
Correct its parameter from mtu to &mtu.
Commit: af8eefea1472de84ef159b89a3b2bc0e650b6b3f
https://github.com/bluez/bluez/commit/af8eefea1472de84ef159b89a3b2bc0e650b6b3f
Author: Zijun Hu <zijun.hu@oss.qualcomm.com>
Date: 2026-07-20 (Mon, 20 Jul 2026)
Changed paths:
M doc/hci-protocol.rst
Log Message:
-----------
doc: hci-protocol: Add sock option BT_RCV_VENDOR_PKT for HCI_CHANNEL_USER
BT_RCV_VENDOR_PKT was introduced to support vendor HCI frame.
Commit: 0108e6e2a4fb4afdab2c3bfd6bb13502e15094ec
https://github.com/bluez/bluez/commit/0108e6e2a4fb4afdab2c3bfd6bb13502e15094ec
Author: Zijun Hu <zijun.hu@oss.qualcomm.com>
Date: 2026-07-20 (Mon, 20 Jul 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: Add generic support for vendor HCI frames
To show vendor HCI frames.
Compare: https://github.com/bluez/bluez/compare/e7eb72a78a58%5E...0108e6e2a4fb
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-20 7:47 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/1130548/000000-0108e6@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