From: Zijun Hu <zijun.hu@oss.qualcomm.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Zijun Hu <zijun_hu@icloud.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bluez RFC 2/3] doc: hci-protocol: Add sock option BT_RCV_VENDOR_PKT for HCI_CHANNEL_USER
Date: Wed, 22 Jul 2026 04:42:02 +0800 [thread overview]
Message-ID: <ca8f0b53-5789-43b4-8a0a-f8b77aace44b@oss.qualcomm.com> (raw)
In-Reply-To: <CABBYNZ+mYA9xgXhXTUdV4C1jM1iFvFSvYAtVUbGavZObGFuhoA@mail.gmail.com>
On 7/21/2026 10:06 PM, Luiz Augusto von Dentz wrote:
>> Hi Luiz,
>>
>> I named it after BT_SNDMTU/BT_RCVMTU, but that may not be a good fit.
>> Any preferred name?
>> Happy to rename.
> I mean we don't need it, you just prefix with packet type 0xff and the
> kernel should accept it.
the socket option is to control if allow kernel to send vendor frame to userspace
its purpose to eliminate regression risk for existing applications
there are no regression risk in userspace to kernel TX direction.
next prev parent reply other threads:[~2026-07-21 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 5:40 [PATCH bluez RFC 0/3] BlueZ: Add generic support for vendor HCI frames Zijun Hu
2026-07-20 5:40 ` [PATCH bluez RFC 1/3] doc: hci-protocol: Correct mtu to &mtu for getsockopt BT_RCVMTU Zijun Hu
2026-07-20 5:40 ` [PATCH bluez RFC 2/3] doc: hci-protocol: Add sock option BT_RCV_VENDOR_PKT for HCI_CHANNEL_USER Zijun Hu
2026-07-20 14:10 ` Luiz Augusto von Dentz
2026-07-21 9:07 ` Zijun Hu
2026-07-21 14:06 ` Luiz Augusto von Dentz
2026-07-21 20:42 ` Zijun Hu [this message]
2026-07-20 5:40 ` [PATCH bluez RFC 3/3] monitor: Add generic support for vendor HCI frames Zijun Hu
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=ca8f0b53-5789-43b4-8a0a-f8b77aace44b@oss.qualcomm.com \
--to=zijun.hu@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=zijun_hu@icloud.com \
/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
all inboxes | Powered by JetHome®