From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iam@sung-woo.kim
Subject: RE: L2CAP: Fix null-ptr-deref in l2cap_sock_set_shutdown_cb
Date: Wed, 18 Jan 2023 18:44:14 -0800 (PST) [thread overview]
Message-ID: <63c8ae7e.050a0220.1969.ec73@mx.google.com> (raw)
In-Reply-To: <20230119013405.3870506-1-iam@sung-woo.kim>
[-- Attachment #1: Type: text/plain, Size: 1597 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=713481
---Test result---
Test Summary:
CheckPatch PASS 1.94 seconds
GitLint PASS 0.34 seconds
SubjectPrefix FAIL 0.53 seconds
BuildKernel PASS 38.21 seconds
CheckAllWarning PASS 41.62 seconds
CheckSparse PASS 46.12 seconds
CheckSmatch PASS 124.89 seconds
BuildKernel32 PASS 36.50 seconds
TestRunnerSetup PASS 513.51 seconds
TestRunner_l2cap-tester PASS 18.77 seconds
TestRunner_iso-tester PASS 19.40 seconds
TestRunner_bnep-tester PASS 6.99 seconds
TestRunner_mgmt-tester PASS 123.49 seconds
TestRunner_rfcomm-tester PASS 10.74 seconds
TestRunner_sco-tester PASS 9.58 seconds
TestRunner_ioctl-tester PASS 10.96 seconds
TestRunner_mesh-tester PASS 8.25 seconds
TestRunner_smp-tester PASS 9.34 seconds
TestRunner_userchan-tester PASS 6.94 seconds
IncrementalBuild PASS 34.93 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-19 2:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 1:34 [PATCH] L2CAP: Fix null-ptr-deref in l2cap_sock_set_shutdown_cb Sungwoo Kim
2023-01-19 1:40 ` BUG: KASAN: null-ptr-deref in _raw_spin_lock_bh+0x4c/0xc0 Sungwoo Kim
2023-01-19 2:04 ` [PATCH] L2CAP: Fix null-ptr-deref in l2cap_sock_set_shutdown_cb Sungwoo Kim
2023-01-19 2:46 ` bluez.test.bot
2023-01-19 3:57 ` BUG: KASAN: null-ptr-deref in _raw_spin_lock_bh+0x4c/0xc0 Eric Dumazet
2023-01-19 2:44 ` bluez.test.bot [this message]
2023-01-19 4:16 ` [PATCH] L2CAP: Fix null-ptr-deref in l2cap_sock_set_shutdown_cb Eric Dumazet
2023-01-20 22:09 ` Luiz Augusto von Dentz
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=63c8ae7e.050a0220.1969.ec73@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iam@sung-woo.kim \
--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 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.