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, raul.cheleguini@gmail.com
Subject: RE: [v2] Bluetooth: Partial support for Actions Semi ATS2851 based devices
Date: Tue, 21 Mar 2023 19:27:55 -0700 (PDT)	[thread overview]
Message-ID: <641a67ab.020a0220.2a7ea.a107@mx.google.com> (raw)
In-Reply-To: <20230322012428.2662664-1-raul.cheleguini@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.39 seconds
GitLint                       PASS      0.28 seconds
SubjectPrefix                 PASS      0.10 seconds
BuildKernel                   PASS      31.21 seconds
CheckAllWarning               PASS      33.98 seconds
CheckSparse                   PASS      38.36 seconds
CheckSmatch                   PASS      107.42 seconds
BuildKernel32                 PASS      29.97 seconds
TestRunnerSetup               PASS      436.34 seconds
TestRunner_l2cap-tester       PASS      16.75 seconds
TestRunner_iso-tester         PASS      16.64 seconds
TestRunner_bnep-tester        PASS      5.37 seconds
TestRunner_mgmt-tester        PASS      108.73 seconds
TestRunner_rfcomm-tester      PASS      8.66 seconds
TestRunner_sco-tester         PASS      7.90 seconds
TestRunner_ioctl-tester       PASS      9.30 seconds
TestRunner_mesh-tester        PASS      6.82 seconds
TestRunner_smp-tester         PASS      7.76 seconds
TestRunner_userchan-tester    PASS      5.57 seconds
IncrementalBuild              PASS      28.24 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: Partial support for Actions Semi ATS2851 based devices
WARNING: quoted string split across lines
#198: FILE: net/bluetooth/hci_sync.c:4534:
 			 "HCI Enhanced Setup Synchronous Connection command is "
+			 "advertised, but not supported."),

WARNING: quoted string split across lines
#201: FILE: net/bluetooth/hci_sync.c:4537:
+			 "HCI LE Set Random Private Address Timeout command is "
+			 "advertised, but not supported."),

total: 0 errors, 2 warnings, 0 checks, 66 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

/github/workspace/src/src/13183456.patch has style problems, please review.

NOTE: Ignored message types: UNKNOWN_COMMIT_ID

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.




---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-03-22  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  1:24 [PATCH v2] Bluetooth: Partial support for Actions Semi ATS2851 based devices Raul Cheleguini
2023-03-22  2:27 ` bluez.test.bot [this message]
2023-03-22  8:00 ` Paul Menzel
2023-03-22 15:07   ` Raul Cheleguini
2023-03-23 15:25     ` Raul Cheleguini

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=641a67ab.020a0220.2a7ea.a107@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=raul.cheleguini@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