All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hildawu@realtek.com
Subject: RE: Bluetooth: btrtl: Add firmware format v3 support and RTL8922D
Date: Fri, 20 Nov 2026 05:26:07 -0800 (PST)	[thread overview]
Message-ID: <6b004a6f.8a6417be.d678f.59f4@mx.google.com> (raw)
In-Reply-To: <20261120082636.3834168-2-hildawu@realtek.com>

[-- Attachment #1: Type: text/plain, Size: 2306 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/series/1217068/

---Test result---

Test Summary:
CheckPatch                    FAIL      2.77 seconds
VerifyFixes                   PASS      0.13 seconds
VerifySignedoff               PASS      0.13 seconds
GitLint                       FAIL      0.65 seconds
SubjectPrefix                 PASS      0.26 seconds
BuildKernel                   PASS      23.75 seconds
CheckAllWarning               PASS      26.96 seconds
CheckSparse                   PASS      29.90 seconds
BuildKernel32                 PASS      23.81 seconds
CheckKernelLLVM               PASS      25.68 seconds
TestRunnerSetup               PASS      551.85 seconds
IncrementalBuild              PASS      25.07 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v10,1/2] Bluetooth: btrtl: Add firmware format v3 support
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#926: 
new file mode 100644

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

/home/runner/work/bluetooth-next/bluetooth-next/src/patch/15004719.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
Desc: Run gitlint
Output:
[v10,1/2] Bluetooth: btrtl: Add firmware format v3 support

29: B1 Line exceeds max length (87>80): "[  174.019929] Bluetooth: hci0: RTL: cfg rtl_bt/rtl8922du_config.bin not found, ignored"
33: B1 Line exceeds max length (96>80): "[  174.019956] Bluetooth: hci0: RTL: cfg rtl_bt/rtl8922du_config_f000.bin not found, use default"
36: B1 Line exceeds max length (96>80): "[  174.019991] Bluetooth: hci0: RTL: cfg rtl_bt/rtl8922du_config_f001.bin not found, use default"


https://github.com/bluez/bluetooth-next/pull/1166

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-11-20 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20  8:26 [PATCH v10 0/2] Bluetooth: btrtl: Add firmware format v3 support and RTL8922D Hilda Wu
2026-11-20  8:26 ` [PATCH v10 1/2] Bluetooth: btrtl: Add firmware format v3 support Hilda Wu
2026-11-20 13:26   ` bluez.test.bot [this message]
2026-11-20  8:26 ` [PATCH v10 2/2] Bluetooth: btrtl: Add the support for RTL8922D Hilda Wu

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=6b004a6f.8a6417be.d678f.59f4@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hildawu@realtek.com \
    --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.