From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, youwan@nfschina.com
Subject: RE: Bluetooth:btusb: Add return error code
Date: Wed, 18 Oct 2023 03:38:05 -0700 (PDT) [thread overview]
Message-ID: <652fb58d.050a0220.6d6ff.12b5@mx.google.com> (raw)
In-Reply-To: <20231018095339.199956-1-youwan@nfschina.com>
[-- Attachment #1: Type: text/plain, Size: 1601 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=794272
---Test result---
Test Summary:
CheckPatch PASS 0.57 seconds
GitLint PASS 0.26 seconds
SubjectPrefix FAIL 0.38 seconds
BuildKernel PASS 33.08 seconds
CheckAllWarning PASS 36.38 seconds
CheckSparse PASS 41.59 seconds
CheckSmatch PASS 116.34 seconds
BuildKernel32 PASS 32.02 seconds
TestRunnerSetup PASS 504.10 seconds
TestRunner_l2cap-tester PASS 29.29 seconds
TestRunner_iso-tester PASS 57.68 seconds
TestRunner_bnep-tester PASS 9.58 seconds
TestRunner_mgmt-tester PASS 210.80 seconds
TestRunner_rfcomm-tester PASS 15.03 seconds
TestRunner_sco-tester PASS 18.49 seconds
TestRunner_ioctl-tester PASS 17.02 seconds
TestRunner_mesh-tester PASS 12.45 seconds
TestRunner_smp-tester PASS 13.36 seconds
TestRunner_userchan-tester PASS 10.16 seconds
IncrementalBuild PASS 31.06 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-10-18 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:53 [PATCH] Bluetooth:btusb: Add return error code youwan
2023-10-18 10:38 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 11:55 [PATCH] Bluetooth: btusb: " youwan
2023-10-18 12:46 ` bluez.test.bot
2023-10-19 2:39 [PATCH] " king
2023-10-19 3:38 ` 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=652fb58d.050a0220.6d6ff.12b5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=youwan@nfschina.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.