linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [1/2] Bluetooth: SCO: Fix possible circular locking dependency on sco_connect_cfm
Date: Thu, 30 Mar 2023 15:35:16 -0700 (PDT)	[thread overview]
Message-ID: <64260ea4.170a0220.85086.0c37@mx.google.com> (raw)
In-Reply-To: <20230330220332.1035910-2-luiz.dentz@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2532 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=735600

---Test result---

Test Summary:
CheckPatch                    PASS      0.65 seconds
GitLint                       FAIL      0.60 seconds
SubjectPrefix                 PASS      0.06 seconds
BuildKernel                   PASS      37.70 seconds
CheckAllWarning               PASS      40.95 seconds
CheckSparse                   WARNING   45.92 seconds
CheckSmatch                   WARNING   125.20 seconds
BuildKernel32                 PASS      36.44 seconds
TestRunnerSetup               PASS      513.59 seconds
TestRunner_l2cap-tester       PASS      17.98 seconds
TestRunner_iso-tester         PASS      18.34 seconds
TestRunner_bnep-tester        PASS      6.32 seconds
TestRunner_mgmt-tester        PASS      121.86 seconds
TestRunner_rfcomm-tester      PASS      9.78 seconds
TestRunner_sco-tester         PASS      8.97 seconds
TestRunner_ioctl-tester       PASS      10.44 seconds
TestRunner_mesh-tester        PASS      7.75 seconds
TestRunner_smp-tester         PASS      8.86 seconds
TestRunner_userchan-tester    PASS      6.47 seconds
IncrementalBuild              PASS      34.31 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/2] Bluetooth: SCO: Fix possible circular locking dependency on sco_connect_cfm

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): "[1/2] Bluetooth: SCO: Fix possible circular locking dependency on sco_connect_cfm"
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:149:35: warning: array of flexible structures
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:149:35: warning: array of flexible structures


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-03-30 22:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 22:03 [PATCH] Bluetooth: Fix double free in hci_conn_cleanup Luiz Augusto von Dentz
2023-03-30 22:03 ` [PATCH 1/2] Bluetooth: SCO: Fix possible circular locking dependency on sco_connect_cfm Luiz Augusto von Dentz
2023-03-30 22:35   ` bluez.test.bot [this message]
2023-03-31 22:10   ` patchwork-bot+bluetooth
2023-03-30 22:03 ` [PATCH 2/2] Bluetooth: SCO: Fix possible circular locking dependency sco_sock_getsockopt Luiz Augusto von Dentz
2023-03-30 22:32 ` Bluetooth: Fix double free in hci_conn_cleanup bluez.test.bot
2023-03-31 22:10 ` [PATCH] " 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=64260ea4.170a0220.85086.0c37@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).