From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, raul.cheleguini@gmail.com
Subject: RE: Bluetooth: Add new quirk for broken extended create connection for ATS2851
Date: Fri, 14 Apr 2023 15:32:01 -0700 (PDT) [thread overview]
Message-ID: <6439d461.050a0220.fd67f.03e5@mx.google.com> (raw)
In-Reply-To: <20230323135804.3962783-1-raul.cheleguini@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2964 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=733189
---Test result---
Test Summary:
CheckPatch FAIL 1.63 seconds
GitLint FAIL 0.60 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 31.32 seconds
CheckAllWarning PASS 34.82 seconds
CheckSparse PASS 39.43 seconds
CheckSmatch PASS 107.85 seconds
BuildKernel32 PASS 30.63 seconds
TestRunnerSetup PASS 435.55 seconds
TestRunner_l2cap-tester PASS 16.84 seconds
TestRunner_iso-tester PASS 17.28 seconds
TestRunner_bnep-tester PASS 5.51 seconds
TestRunner_mgmt-tester PASS 114.76 seconds
TestRunner_rfcomm-tester PASS 8.82 seconds
TestRunner_sco-tester PASS 8.15 seconds
TestRunner_ioctl-tester PASS 9.49 seconds
TestRunner_mesh-tester PASS 6.95 seconds
TestRunner_smp-tester PASS 8.00 seconds
TestRunner_userchan-tester PASS 5.81 seconds
IncrementalBuild PASS 29.21 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: Add new quirk for broken extended create connection for ATS2851
WARNING: Use lore.kernel.org archive links when possible - see https://lore.kernel.org/lists.html
#109:
[1]. https://marc.info/?l=linux-bluetooth&m=167957918920723&w=2
WARNING: quoted string split across lines
#169: FILE: net/bluetooth/hci_sync.c:4537:
"HCI LE Set Random Private Address Timeout command is "
+ "advertised, but not supported."),
total: 0 errors, 2 warnings, 0 checks, 45 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/13185667.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:
Bluetooth: Add new quirk for broken extended create connection for ATS2851
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
33: B2 Line has trailing whitespace: " "
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-04-14 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 13:58 [PATCH] Bluetooth: Add new quirk for broken extended create connection for ATS2851 Raul Cheleguini
2023-03-23 14:13 ` bluez.test.bot
2023-04-14 22:32 ` bluez.test.bot [this message]
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=6439d461.050a0220.fd67f.03e5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=raul.cheleguini@gmail.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.