From: Zijun Hu <zijun.hu@oss.qualcomm.com>
To: Pauli Virtanen <pav@iki.fi>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Zijun Hu <zijun_hu@icloud.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072
Date: Mon, 14 Sep 2026 10:53:32 +0800 [thread overview]
Message-ID: <6e3de792-85c3-4264-9d1d-cdbb8f6ed025@oss.qualcomm.com> (raw)
In-Reply-To: <7bfc5ec0438b830386ae2899756bb9a7c4b9e123.camel@iki.fi>
On 9/12/2026 3:56 AM, Pauli Virtanen wrote:
>> +/*
>> + * btusb_qcom_send_frame - send a frame for BT or PERI
>> + * @hdev: the HCI device
>> + * @skb: the frame to send
>> + *
>> + * Implements hdev->send().
>> + *
>> + * Return: 0 on success, or a negative errno on failure.
>> + */
>> +int btusb_qcom_send_frame(struct hci_dev *hdev, struct sk_buff *skb)
> This one should have __context_unsafe(/* conditional locking */)
> annotation, or no if (need_lock), to avoid warnings on LLVM 23.
Good catch — fixed in v6 (below) by adding the __context_unsafe(/* conditional locking */)
annotation, per your suggestion.
https://lore.kernel.org/all/20260913-btusb_qcc2072-v6-0-137898715844@oss.qualcomm.com
prev parent reply other threads:[~2026-09-14 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 8:00 [PATCH v5 0/4] Bluetooth: btusb: Support " Zijun Hu
2026-09-11 8:00 ` [PATCH v5 1/4] Bluetooth: btusb: Add recv_intr() hook to btusb_data Zijun Hu
2026-09-11 8:00 ` [PATCH v5 2/4] Bluetooth: Add generic support for vendor packets Zijun Hu
2026-09-11 8:00 ` [PATCH v5 3/4] Bluetooth: btusb: Build the driver from multiple source files Zijun Hu
2026-09-11 8:00 ` [PATCH v5 4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072 Zijun Hu
2026-09-11 19:56 ` Pauli Virtanen
2026-09-14 2:53 ` Zijun Hu [this message]
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=6e3de792-85c3-4264-9d1d-cdbb8f6ed025@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=pav@iki.fi \
--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®