All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, william.xuanziyang@huawei.com
Subject: RE: Bluetooth: Fix a refcnt underflow problem for hci_conn
Date: Wed, 04 Oct 2023 06:25:39 -0700 (PDT)	[thread overview]
Message-ID: <651d67d3.c80a0220.9d145.615d@mx.google.com> (raw)
In-Reply-To: <20231004124224.630914-1-william.xuanziyang@huawei.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.81 seconds
GitLint                       FAIL      0.65 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      43.45 seconds
CheckAllWarning               PASS      45.87 seconds
CheckSparse                   WARNING   53.57 seconds
CheckSmatch                   WARNING   154.17 seconds
BuildKernel32                 PASS      44.99 seconds
TestRunnerSetup               PASS      652.20 seconds
TestRunner_l2cap-tester       PASS      37.78 seconds
TestRunner_iso-tester         PASS      94.68 seconds
TestRunner_bnep-tester        PASS      13.16 seconds
TestRunner_mgmt-tester        PASS      266.03 seconds
TestRunner_rfcomm-tester      PASS      20.14 seconds
TestRunner_sco-tester         PASS      23.29 seconds
TestRunner_ioctl-tester       PASS      23.21 seconds
TestRunner_mesh-tester        PASS      17.11 seconds
TestRunner_smp-tester         PASS      17.68 seconds
TestRunner_userchan-tester    PASS      13.96 seconds
IncrementalBuild              PASS      38.79 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: Fix a refcnt underflow problem for hci_conn

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
5: B1 Line exceeds max length (116>80): "WARNING: CPU: 1 PID: 26946 at net/bluetooth/hci_conn.c:619 hci_conn_timeout+0x122/0x210 net/bluetooth/hci_conn.c:619"
##############################
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


  reply	other threads:[~2023-10-04 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 12:42 [PATCH] Bluetooth: Fix a refcnt underflow problem for hci_conn Ziyang Xuan
2023-10-04 13:25 ` bluez.test.bot [this message]
2023-10-04 19: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=651d67d3.c80a0220.9d145.615d@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=william.xuanziyang@huawei.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.