Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: MGMT: Reject quality report requests during unregister
Date: Tue, 06 Oct 2026 01:32:34 -0700 (PDT)	[thread overview]
Message-ID: <6ac4b222.695ff321.f867b.1d42@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0186-v1-e03b4f1d5ba49b962cec@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2926 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/1180100/

---Test result---

Test Summary:
CheckPatch                    FAIL      13.83 seconds
VerifyFixes                   PASS      0.17 seconds
VerifySignedoff               PASS      0.09 seconds
GitLint                       FAIL      0.39 seconds
SubjectPrefix                 PASS      0.09 seconds
BuildKernel                   PASS      22.40 seconds
CheckAllWarning               PASS      29.54 seconds
CheckSparse                   PASS      29.26 seconds
BuildKernel32                 PASS      24.17 seconds
CheckKernelLLVM               PASS      26.56 seconds
TestRunnerSetup               PASS      585.71 seconds
TestRunner_mgmt-tester        PASS      56.87 seconds
TestRunner_mesh-tester        FAIL      7.69 seconds
IncrementalBuild              PASS      22.60 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: MGMT: Reject quality report requests during unregister
WARNING: The commit message has 'Call Trace:', perhaps it also needs a 'Fixes:' tag?

total: 0 errors, 1 warnings, 0 checks, 13 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/14869362.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:
Bluetooth: MGMT: Reject quality report requests during unregister

46: B2 Line has trailing whitespace: "    PGD 80a9067 P4D 80a9067 PUD 80ab067 PMD 0 "
48: B1 Line exceeds max length (119>80): "    CPU: 1 UID: 0 PID: 439 Comm: btmgmt Tainted: G           O        7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy) "
48: B2 Line has trailing whitespace: "    CPU: 1 UID: 0 PID: 439 Comm: btmgmt Tainted: G           O        7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy) "
50: B1 Line exceeds max length (119>80): "    Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014"
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Timed out    2.637 seconds
Mesh - Send cancel - 2                               Timed out    1.999 seconds


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-10-06  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06  7:24 [PATCH] Bluetooth: MGMT: Reject quality report requests during unregister Cen Zhang
2026-10-06  8:32 ` bluez.test.bot [this message]
2026-10-07 17:30 ` 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=6ac4b222.695ff321.f867b.1d42@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zzzccc427@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