From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: MGMT: Fix marking SCAN_RSP as not connectable
Date: Wed, 07 Jun 2023 13:38:19 -0700 (PDT) [thread overview]
Message-ID: <6480eabb.170a0220.fc604.5a93@mx.google.com> (raw)
In-Reply-To: <20230607194518.2901376-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2481 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=755036
---Test result---
Test Summary:
CheckPatch PASS 0.88 seconds
GitLint FAIL 0.67 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 43.40 seconds
CheckAllWarning PASS 46.08 seconds
CheckSparse WARNING 51.88 seconds
CheckSmatch WARNING 142.87 seconds
BuildKernel32 PASS 42.15 seconds
TestRunnerSetup PASS 592.76 seconds
TestRunner_l2cap-tester PASS 20.87 seconds
TestRunner_iso-tester PASS 30.92 seconds
TestRunner_bnep-tester PASS 7.51 seconds
TestRunner_mgmt-tester PASS 146.19 seconds
TestRunner_rfcomm-tester PASS 11.75 seconds
TestRunner_sco-tester PASS 10.98 seconds
TestRunner_ioctl-tester PASS 13.07 seconds
TestRunner_mesh-tester PASS 9.55 seconds
TestRunner_smp-tester PASS 10.71 seconds
TestRunner_userchan-tester PASS 7.93 seconds
IncrementalBuild PASS 39.33 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: MGMT: Fix marking SCAN_RSP as not connectable
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
11: B1 Line exceeds max length (113>80): "Link: https://lore.kernel.org/linux-bluetooth/CABBYNZ+CYMsDSPTxBn09Js3BcdC-x7vZFfyLJ3ppZGGwJKmUTw@mail.gmail.com/"
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-06-07 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 19:45 [PATCH] Bluetooth: MGMT: Fix marking SCAN_RSP as not connectable Luiz Augusto von Dentz
2023-06-07 20:38 ` bluez.test.bot [this message]
2023-06-20 18:30 ` patchwork-bot+bluetooth
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=6480eabb.170a0220.fc604.5a93@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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.