All of lore.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: [v1] Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST
Date: Mon, 22 Jan 2024 09:02:55 -0800 (PST)	[thread overview]
Message-ID: <65ae9fbf.050a0220.e7652.37d4@mx.google.com> (raw)
In-Reply-To: <20240122161521.2650805-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.52 seconds
GitLint                       FAIL      0.55 seconds
SubjectPrefix                 PASS      0.09 seconds
BuildKernel                   PASS      28.24 seconds
CheckAllWarning               PASS      30.11 seconds
CheckSparse                   WARNING   46.14 seconds
CheckSmatch                   WARNING   105.09 seconds
BuildKernel32                 PASS      34.58 seconds
TestRunnerSetup               PASS      429.32 seconds
TestRunner_l2cap-tester       PASS      32.05 seconds
TestRunner_iso-tester         PASS      52.07 seconds
TestRunner_bnep-tester        PASS      14.42 seconds
TestRunner_mgmt-tester        PASS      155.89 seconds
TestRunner_rfcomm-tester      PASS      17.83 seconds
TestRunner_sco-tester         PASS      18.38 seconds
TestRunner_ioctl-tester       PASS      15.94 seconds
TestRunner_mesh-tester        PASS      13.33 seconds
TestRunner_smp-tester         PASS      15.40 seconds
TestRunner_userchan-tester    PASS      10.14 seconds
IncrementalBuild              PASS      38.22 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v1] Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST

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
9: B1 Line exceeds max length (117>80): "Link: https://lore.kernel.org/linux-bluetooth/CABBYNZ+9UdG1cMZVmdtN3U2aS16AKMCyTARZZyFX7xTEDWcMOw@mail.gmail.com/T/#t"
##############################
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:[~2024-01-22 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 16:15 [PATCH v1] Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST Luiz Augusto von Dentz
2024-01-22 17:02 ` bluez.test.bot [this message]
2024-01-25 20:50 ` 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=65ae9fbf.050a0220.e7652.37d4@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.