From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, en-wei.wu@canonical.com
Subject: RE: btusb: fix NULL pointer dereference in QCA devcoredump handling
Date: Mon, 21 Apr 2025 07:01:56 -0700 (PDT) [thread overview]
Message-ID: <68064fd4.9d0a0220.2b8775.fe6a@mx.google.com> (raw)
In-Reply-To: <20250421130038.34998-2-en-wei.wu@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1681 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/project/bluetooth/list/?series=955286
---Test result---
Test Summary:
CheckPatch PENDING 0.33 seconds
GitLint PENDING 0.25 seconds
SubjectPrefix PASS 0.17 seconds
BuildKernel PASS 24.43 seconds
CheckAllWarning PASS 26.77 seconds
CheckSparse PASS 30.50 seconds
BuildKernel32 PASS 24.04 seconds
TestRunnerSetup PASS 457.88 seconds
TestRunner_l2cap-tester PASS 21.04 seconds
TestRunner_iso-tester PASS 35.13 seconds
TestRunner_bnep-tester PASS 4.75 seconds
TestRunner_mgmt-tester PASS 122.35 seconds
TestRunner_rfcomm-tester PASS 7.82 seconds
TestRunner_sco-tester PASS 12.60 seconds
TestRunner_ioctl-tester PASS 8.36 seconds
TestRunner_mesh-tester PASS 6.08 seconds
TestRunner_smp-tester PASS 7.18 seconds
TestRunner_userchan-tester PASS 5.04 seconds
IncrementalBuild PENDING 0.56 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-04-21 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 13:00 [PATCH v4 0/2] btusb: fix NULL pointer dereference in QCA devcoredump handling En-Wei Wu
2025-04-21 13:00 ` [PATCH v4 1/2] Bluetooth: btusb: avoid NULL pointer dereference in skb_dequeue() En-Wei Wu
2025-04-21 14:01 ` bluez.test.bot [this message]
2025-04-21 13:00 ` [PATCH v4 2/2] Bluetooth: btusb: use skb_pull to avoid unsafe access in QCA dump handling En-Wei Wu
2025-04-21 15:29 ` Luiz Augusto von Dentz
2025-04-21 19:17 ` [PATCH v4 0/2] btusb: fix NULL pointer dereference in QCA devcoredump handling Luiz Augusto von Dentz
2025-04-24 1:46 ` En-Wei WU
2025-04-24 1:49 ` En-Wei WU
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=68064fd4.9d0a0220.2b8775.fe6a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=en-wei.wu@canonical.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