linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zheyuma97@gmail.com
Subject: RE: bluetooth: bfusb: Check the endpoint type at probe
Date: Fri, 13 May 2022 06:48:36 -0700 (PDT)	[thread overview]
Message-ID: <627e61b4.1c69fb81.40c5f.731e@mx.google.com> (raw)
In-Reply-To: <20220513124303.2192981-1-zheyuma97@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.62 seconds
GitLint                       FAIL      1.00 seconds
SubjectPrefix                 FAIL      0.85 seconds
BuildKernel                   PASS      37.39 seconds
BuildKernel32                 PASS      32.48 seconds
Incremental Build with patchesPASS      43.17 seconds
TestRunner: Setup             PASS      542.39 seconds
TestRunner: l2cap-tester      PASS      19.03 seconds
TestRunner: bnep-tester       PASS      6.79 seconds
TestRunner: mgmt-tester       PASS      116.84 seconds
TestRunner: rfcomm-tester     PASS      10.85 seconds
TestRunner: sco-tester        PASS      10.37 seconds
TestRunner: smp-tester        PASS      10.63 seconds
TestRunner: userchan-tester   PASS      7.00 seconds

Details
##############################
Test: GitLint - FAIL - 1.00 seconds
Run gitlint with rule in .gitlint
bluetooth: bfusb: Check the endpoint type at probe
7: B1 Line exceeds max length (96>80): "[    3.295916] WARNING: CPU: 0 PID: 33 at drivers/usb/core/urb.c:503 usb_submit_urb+0xcd9/0x18b0"


##############################
Test: SubjectPrefix - FAIL - 0.85 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2022-05-13 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 12:43 [PATCH] bluetooth: bfusb: Check the endpoint type at probe Zheyu Ma
2022-05-13 12:53 ` Marcel Holtmann
2022-05-13 13:25   ` Zheyu Ma
2022-05-13 13:48 ` bluez.test.bot [this message]
2022-05-13 14:07 ` [PATCH v2] Bluetooth: " Zheyu Ma
2022-05-13 14:39   ` [v2] " bluez.test.bot

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=627e61b4.1c69fb81.40c5f.731e@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zheyuma97@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).