From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, herbert@gondor.apana.org.au
Subject: RE: KEYS: Include linux/errno.h in linux/verification.h
Date: Sat, 26 Aug 2023 02:35:39 -0700 (PDT) [thread overview]
Message-ID: <64e9c76b.0c0a0220.7c741.4782@mx.google.com> (raw)
In-Reply-To: <ZOm5mX0+oUGzO3xh@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 3150 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=779564
---Test result---
Test Summary:
CheckPatch FAIL 1.18 seconds
GitLint FAIL 0.64 seconds
SubjectPrefix FAIL 0.37 seconds
BuildKernel PASS 34.28 seconds
CheckAllWarning PASS 37.34 seconds
CheckSparse PASS 42.76 seconds
CheckSmatch PASS 115.58 seconds
BuildKernel32 PASS 32.92 seconds
TestRunnerSetup PASS 501.03 seconds
TestRunner_l2cap-tester PASS 28.86 seconds
TestRunner_iso-tester PASS 51.48 seconds
TestRunner_bnep-tester PASS 11.30 seconds
TestRunner_mgmt-tester PASS 225.81 seconds
TestRunner_rfcomm-tester PASS 16.97 seconds
TestRunner_sco-tester PASS 20.59 seconds
TestRunner_ioctl-tester PASS 19.16 seconds
TestRunner_mesh-tester PASS 14.39 seconds
TestRunner_smp-tester PASS 15.43 seconds
TestRunner_userchan-tester PASS 12.02 seconds
IncrementalBuild PASS 31.39 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
KEYS: Include linux/errno.h in linux/verification.h
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#77:
> >> include/linux/verification.h:23:11: error: use of undeclared identifier 'EINVAL'
total: 0 errors, 1 warnings, 7 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/src/13366546.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
KEYS: Include linux/errno.h in linux/verification.h
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
6: B2 Line has trailing whitespace: "> "
8: B1 Line exceeds max length (85>80): "> >> include/linux/verification.h:23:11: error: use of undeclared identifier 'EINVAL'"
15: B1 Line exceeds max length (82>80): "Closes: https://lore.kernel.org/oe-kbuild-all/202308261414.HKw1Mrip-lkp@intel.com/"
##############################
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-08-26 9:36 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 10:30 [PATCH 0/12] Do not include crypto/algapi.h Herbert Xu
2023-08-23 10:30 ` Herbert Xu
2023-08-23 10:32 ` [PATCH 1/12] fscrypt: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-25 21:13 ` Eric Biggers
2023-08-25 21:13 ` Eric Biggers
2023-08-23 10:32 ` [PATCH 2/12] ubifs: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-26 6:58 ` kernel test robot
2023-08-26 6:58 ` kernel test robot
2023-08-26 8:36 ` [PATCH] KEYS: Include linux/errno.h in linux/verification.h Herbert Xu
2023-08-26 8:36 ` Herbert Xu
2023-08-26 9:35 ` bluez.test.bot [this message]
2023-08-28 9:33 ` Daniel Borkmann
2023-08-28 9:33 ` Daniel Borkmann
2023-08-27 1:40 ` [PATCH 2/12] ubifs: Do not include crypto/algapi.h kernel test robot
2023-08-27 1:40 ` kernel test robot
2023-08-23 10:32 ` [PATCH 3/12] Bluetooth: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-25 21:23 ` Luiz Augusto von Dentz
2023-08-25 21:23 ` Luiz Augusto von Dentz
2023-08-23 10:32 ` [PATCH 4/12] ceph: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-23 20:53 ` Ilya Dryomov
2023-08-23 20:53 ` Ilya Dryomov
2023-08-23 10:32 ` [PATCH 5/12] ah: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-23 10:32 ` [PATCH 6/12] wifi: mac80211: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-23 10:34 ` Johannes Berg
2023-08-23 10:34 ` Johannes Berg
2023-08-24 5:10 ` Herbert Xu
2023-08-24 5:10 ` Herbert Xu
2023-08-24 6:59 ` Johannes Berg
2023-08-24 6:59 ` Johannes Berg
2023-08-24 8:45 ` Herbert Xu
2023-08-24 8:45 ` Herbert Xu
2023-08-23 10:32 ` [PATCH 7/12] mptcp: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-23 12:53 ` Matthieu Baerts
2023-08-23 12:53 ` Matthieu Baerts
2023-08-23 10:32 ` [PATCH 8/12] SUNRPC: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-23 13:44 ` Chuck Lever
2023-08-23 13:44 ` Chuck Lever
2023-08-23 10:32 ` [PATCH 9/12] evm: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-24 23:57 ` Mimi Zohar
2023-08-24 23:57 ` Mimi Zohar
2023-08-23 10:32 ` [PATCH 10/12] KEYS: encrypted: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-24 23:57 ` Mimi Zohar
2023-08-24 23:57 ` Mimi Zohar
2023-08-23 10:32 ` [PATCH 11/12] wireguard: " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
2023-08-23 11:48 ` Jason A. Donenfeld
2023-08-23 11:48 ` Jason A. Donenfeld
2023-08-24 5:17 ` [v2 PATCH] wireguard: do " Herbert Xu
2023-08-23 10:32 ` [PATCH 12/12] chelsio: Do " Herbert Xu
2023-08-23 10:32 ` Herbert Xu
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=64e9c76b.0c0a0220.7c741.4782@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=herbert@gondor.apana.org.au \
--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.