All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: RE: New BT devices from the Realtek rtw89 family
Date: Tue, 16 Aug 2022 15:01:36 -0700 (PDT)	[thread overview]
Message-ID: <62fc13c0.170a0220.4bec.0582@mx.google.com> (raw)
In-Reply-To: <20220816213523.5207-2-Larry.Finger@lwfinger.net>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.80 seconds
GitLint                       FAIL      1.08 seconds
SubjectPrefix                 PASS      0.79 seconds
BuildKernel                   PASS      33.37 seconds
BuildKernel32                 PASS      28.31 seconds
Incremental Build with patchesPASS      48.11 seconds
TestRunner: Setup             PASS      479.04 seconds
TestRunner: l2cap-tester      PASS      16.44 seconds
TestRunner: bnep-tester       PASS      6.10 seconds
TestRunner: mgmt-tester       PASS      99.29 seconds
TestRunner: rfcomm-tester     PASS      9.36 seconds
TestRunner: sco-tester        PASS      9.12 seconds
TestRunner: smp-tester        PASS      9.20 seconds
TestRunner: userchan-tester   PASS      6.28 seconds

Details
##############################
Test: CheckPatch - FAIL - 1.80 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[2/2] Bluetooth: btusb: Add BT devices 0bda:4853 and 0bda:887b from RTW8852BE to tables\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#92: 
Bus 003 Device 004: ID 0bda:4853 Realtek Semiconductor Corp. Bluetooth Radio

total: 0 errors, 1 warnings, 12 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/12945318.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.


##############################
Test: GitLint - FAIL - 1.08 seconds
Run gitlint with rule in .gitlint
[2/2] Bluetooth: btusb: Add BT devices 0bda:4853 and 0bda:887b from RTW8852BE to tables
1: T1 Title exceeds max length (87>80): "[2/2] Bluetooth: btusb: Add BT devices 0bda:4853 and 0bda:887b from RTW8852BE to tables"




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-08-16 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 21:35 [PATCH 0/2] New BT devices from the Realtek rtw89 family Larry Finger
2022-08-16 21:35 ` [PATCH 1/2] Bluetooth: btusb: Add BT device 0cb8:c549 from RTW8852AE to tables Larry Finger
2022-08-16 22:01   ` bluez.test.bot [this message]
2022-08-16 21:35 ` [PATCH 2/2] Bluetooth: btusb: Add BT devices 0bda:4853 and 0bda:887b from RTW8852BE " Larry Finger
2022-08-31 23:10 ` [PATCH 0/2] New BT devices from the Realtek rtw89 family 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=62fc13c0.170a0220.4bec.0582@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.