From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: Bluetooth: Add generic support for vendor HCI frames
Date: Wed, 22 Jul 2026 09:43:06 -0700 (PDT) [thread overview]
Message-ID: <6a60f31a.1fd19957.28a4f.de7e@mx.google.com> (raw)
In-Reply-To: <20260722-support_vendor_hci-v2-1-132b506460a4@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
This is an automated email and please do not reply to this email.
Dear Submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository.
----- Output -----
error: patch failed: net/bluetooth/hci_core.c:4057
error: net/bluetooth/hci_core.c: patch does not apply
hint: Use 'git am --show-current-patch' to see the failed patch
Please resolve the issue and submit the patches again.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-22 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 16:24 [PATCH RFC v2 0/3] Bluetooth: Add generic support for vendor HCI frames Zijun Hu
2026-07-22 16:24 ` [PATCH RFC v2 1/3] Bluetooth: btmrvl_sdio: Do not free HCI_VENDOR_PKT frame by hci_recv_frame() Zijun Hu
2026-07-22 16:43 ` bluez.test.bot [this message]
2026-07-22 16:24 ` [PATCH RFC v2 2/3] Bluetooth: Add generic support for vendor HCI frames using HCI_VENDOR_PKT Zijun Hu
2026-07-22 16:24 ` [PATCH RFC v2 3/3] Bluetooth: Add hdev->recv_bt_vendor() to handle BT vendor frames Zijun Hu
2026-07-22 16:46 ` Luiz Augusto von Dentz
[not found] ` <c17cedf9-a013-4ba1-be0e-46f5650ddd89@oss.qualcomm.com>
2026-07-23 13:56 ` Luiz Augusto von Dentz
2026-07-23 18:52 ` Zijun Hu
2026-07-27 18:30 ` [PATCH RFC v2 0/3] Bluetooth: Add generic support for vendor HCI frames patchwork-bot+bluetooth
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=6a60f31a.1fd19957.28a4f.de7e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zijun.hu@oss.qualcomm.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