From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [v2,1/2] Bluetooth: hci_sync: always check if connection is alive before deleting
Date: Sat, 30 Sep 2023 06:36:39 -0700 (PDT) [thread overview]
Message-ID: <65182467.4a0a0220.e243c.ed61@mx.google.com> (raw)
In-Reply-To: <53130b4a5fb21a15f2674c336282d25ef5d2232e.1696077070.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2942 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=789014
---Test result---
Test Summary:
CheckPatch PASS 1.53 seconds
GitLint FAIL 0.86 seconds
SubjectPrefix PASS 0.20 seconds
BuildKernel PASS 33.69 seconds
CheckAllWarning PASS 36.16 seconds
CheckSparse PASS 41.46 seconds
CheckSmatch PASS 115.45 seconds
BuildKernel32 PASS 31.93 seconds
TestRunnerSetup PASS 489.12 seconds
TestRunner_l2cap-tester PASS 30.32 seconds
TestRunner_iso-tester PASS 49.69 seconds
TestRunner_bnep-tester PASS 9.79 seconds
TestRunner_mgmt-tester PASS 214.41 seconds
TestRunner_rfcomm-tester PASS 14.96 seconds
TestRunner_sco-tester PASS 18.53 seconds
TestRunner_ioctl-tester PASS 16.93 seconds
TestRunner_mesh-tester PASS 12.59 seconds
TestRunner_smp-tester PASS 13.38 seconds
TestRunner_userchan-tester PASS 10.31 seconds
IncrementalBuild PASS 37.23 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2,1/2] Bluetooth: hci_sync: always check if connection is alive before deleting
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
1: T1 Title exceeds max length (81>80): "[v2,1/2] Bluetooth: hci_sync: always check if connection is alive before deleting"
[v2,2/2] Bluetooth: hci_conn: verify connection is to be aborted before doing it
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
18: B1 Line exceeds max length (88>80): "Closes: https://lore.kernel.org/linux-bluetooth/0000000000005ab984060371583e@google.com/"
31: B3 Line contains hard tab characters (\t): " 2874 conn = hci_conn_hash_lookup_handle(hdev, handle);"
32: B3 Line contains hard tab characters (\t): " 2875 if (!conn || WARN_ON(!conn->abort_reason))"
33: B3 Line contains hard tab characters (\t): " 2876 return 0;"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-09-30 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 12:53 [PATCH v2 1/2] Bluetooth: hci_sync: always check if connection is alive before deleting Pauli Virtanen
2023-09-30 12:53 ` [PATCH v2 2/2] Bluetooth: hci_conn: verify connection is to be aborted before doing it Pauli Virtanen
2023-09-30 13:28 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in hci_send_acl syzbot
2023-10-02 23:22 ` [PATCH v2 2/2] Bluetooth: hci_conn: verify connection is to be aborted before doing it Luiz Augusto von Dentz
2023-10-03 16:41 ` Pauli Virtanen
2023-09-30 13:36 ` bluez.test.bot [this message]
2023-10-03 17:10 ` [PATCH v2 1/2] Bluetooth: hci_sync: always check if connection is alive before deleting 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=65182467.4a0a0220.e243c.ed61@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.