From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, tzungbi@kernel.org
Subject: RE: Bluetooth: btrtl: Fix NULL return on errors in btrtl_initialize()
Date: Tue, 27 Oct 2026 04:25:43 -0700 (PDT) [thread overview]
Message-ID: <6ae08a37.3e00a709.ec3be.7cf2@mx.google.com> (raw)
In-Reply-To: <20261027072148.3963826-2-tzungbi@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1460 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/1194330/
---Test result---
Test Summary:
CheckPatch PASS 1.03 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.10 seconds
GitLint FAIL 3.35 seconds
SubjectPrefix PASS 0.20 seconds
BuildKernel PASS 19.01 seconds
CheckAllWarning PASS 22.73 seconds
CheckSparse PASS 25.28 seconds
BuildKernel32 PASS 19.43 seconds
CheckKernelLLVM PASS 20.21 seconds
TestRunnerSetup PASS 452.76 seconds
IncrementalBuild PASS 20.34 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/2] Bluetooth: btrtl: Propagate errors if btrtl_vendor_read_reg16() fails
5: B1 Line exceeds max length (94>80): " [ 2592.730992] Bluetooth: btrtl_vendor_read_reg16() hci0: RTL: RTL: Read reg16 failed (-110)"
6: B1 Line exceeds max length (99>80): " [ 2592.731005] Bluetooth: btusb_rtl_alloc_devcoredump() hci0: RTL: Failed to generate devcoredump"
https://github.com/bluez/bluetooth-next/pull/1005
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-27 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 7:21 [PATCH 0/2] Bluetooth: btrtl: Fix NULL return on errors in btrtl_initialize() Tzung-Bi Shih
2026-10-27 7:21 ` [PATCH 1/2] Bluetooth: btrtl: Propagate errors if btrtl_vendor_read_reg16() fails Tzung-Bi Shih
2026-10-27 11:25 ` bluez.test.bot [this message]
2026-10-27 7:21 ` [PATCH 2/2] Bluetooth: btrtl: Return -ENOMEM if bt_skb_alloc() fails Tzung-Bi Shih
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=6ae08a37.3e00a709.ec3be.7cf2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tzungbi@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.