public inbox for linux-bluetooth@vger.kernel.org
 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: hci_conn: Fix not cleaning up on LE Connection failure
Date: Fri, 24 Mar 2023 14:38:26 -0700 (PDT)	[thread overview]
Message-ID: <641e1852.050a0220.7005f.4da5@mx.google.com> (raw)
In-Reply-To: <20230324204525.3630188-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      2.34 seconds
GitLint                       PASS      0.77 seconds
SubjectPrefix                 PASS      0.28 seconds
BuildKernel                   PASS      44.46 seconds
CheckAllWarning               PASS      48.86 seconds
CheckSparse                   WARNING   55.16 seconds
CheckSmatch                   WARNING   146.37 seconds
BuildKernel32                 PASS      43.09 seconds
TestRunnerSetup               PASS      612.31 seconds
TestRunner_l2cap-tester       PASS      20.91 seconds
TestRunner_iso-tester         PASS      22.25 seconds
TestRunner_bnep-tester        PASS      7.47 seconds
TestRunner_mgmt-tester        PASS      136.93 seconds
TestRunner_rfcomm-tester      PASS      11.60 seconds
TestRunner_sco-tester         PASS      10.57 seconds
TestRunner_ioctl-tester       PASS      12.56 seconds
TestRunner_mesh-tester        PASS      9.31 seconds
TestRunner_smp-tester         PASS      10.44 seconds
TestRunner_userchan-tester    PASS      7.80 seconds
IncrementalBuild              PASS      76.85 seconds

Details
##############################
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


  parent reply	other threads:[~2023-03-24 21:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 20:45 [PATCH 1/2] Bluetooth: hci_conn: Fix not cleaning up on LE Connection failure Luiz Augusto von Dentz
2023-03-24 20:45 ` [PATCH 2/2] Bluetooth: Fix printing errors if LE Connection times out Luiz Augusto von Dentz
2023-03-24 21:38 ` bluez.test.bot [this message]
2023-03-25  0:06 ` [PATCH 1/2] Bluetooth: hci_conn: Fix not cleaning up on LE Connection failure kernel test robot
2023-03-27 14:23 ` Dan Carpenter

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=641e1852.050a0220.7005f.4da5@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