From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: Bluetooth: btnxpuart: Simplify ACL handling and fix skb leak
Date: Tue, 15 Sep 2026 23:06:02 -0700 (PDT) [thread overview]
Message-ID: <6aaa31ca.54e42a5c.3b22cc.8022@mx.google.com> (raw)
In-Reply-To: <20260915-misc_fix-v3-1-31fab8976ac1@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1166013/
---Test result---
Test Summary:
CheckPatch PASS 1.08 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.08 seconds
GitLint PASS 0.50 seconds
SubjectPrefix PASS 0.56 seconds
BuildKernel PASS 26.24 seconds
CheckAllWarning PASS 31.20 seconds
CheckSparse PASS 33.19 seconds
BuildKernel32 PASS 26.67 seconds
CheckKernelLLVM PASS 30.04 seconds
TestRunnerSetup PASS 673.08 seconds
IncrementalBuild PASS 26.61 seconds
https://github.com/bluez/bluetooth-next/pull/780
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-16 6:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 2:17 [PATCH v3 0/2] Bluetooth: btnxpuart: Simplify ACL handling and fix skb leak Zijun Hu
2026-09-16 2:17 ` [PATCH v3 1/2] Bluetooth: btnxpuart: Simplify nxp_recv_acl_pkt() by hci_acl_handle() Zijun Hu
2026-09-16 6:06 ` bluez.test.bot [this message]
2026-09-16 2:17 ` [PATCH v3 2/2] Bluetooth: btnxpuart: Fix skb leak in nxp_process_fw_dump() Zijun Hu
-- strict thread matches above, loose matches on Subject: below --
2026-09-15 5:40 [PATCH v2 1/2] Bluetooth: btnxpuart: Simplify nxp_recv_acl_pkt() by hci_acl_handle() Zijun Hu
2026-09-15 7:25 ` Bluetooth: btnxpuart: Simplify ACL handling and fix skb leak bluez.test.bot
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=6aaa31ca.54e42a5c.3b22cc.8022@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 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.