All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: msft: Lock failed probe cleanup against feature readers
Date: Tue, 06 Oct 2026 08:31:19 -0700 (PDT)	[thread overview]
Message-ID: <6ac51447.c02443da.c755a.558c@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0233-v3-004a766561f1356a1b14@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.69 seconds
VerifyFixes                   PASS      0.09 seconds
VerifySignedoff               PASS      0.17 seconds
GitLint                       FAIL      0.26 seconds
SubjectPrefix                 PASS      0.09 seconds
BuildKernel                   PASS      32.19 seconds
CheckAllWarning               PASS      33.73 seconds
CheckSparse                   PASS      36.83 seconds
BuildKernel32                 PASS      29.44 seconds
CheckKernelLLVM               PASS      34.96 seconds
TestRunnerSetup               PASS      831.76 seconds
TestRunner_l2cap-tester       PASS      12.72 seconds
TestRunner_iso-tester         PASS      15.67 seconds
TestRunner_bnep-tester        PASS      3.09 seconds
TestRunner_mgmt-tester        PASS      61.35 seconds
TestRunner_rfcomm-tester      PASS      4.42 seconds
TestRunner_sco-tester         PASS      5.58 seconds
TestRunner_ioctl-tester       PASS      4.64 seconds
TestRunner_mesh-tester        PASS      5.50 seconds
TestRunner_smp-tester         PASS      4.29 seconds
TestRunner_userchan-tester    PASS      3.17 seconds
TestRunner_6lowpan-tester     PASS      4.40 seconds
IncrementalBuild              PASS      32.64 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: msft: Lock failed probe cleanup against feature readers

39: B2 Line has trailing whitespace: "    "
40: B2 Line has trailing whitespace: "        CPU: 2 UID: 0 PID: 532 Comm: mgmt-read-adv-m Not tainted "
41: B2 Line has trailing whitespace: "    7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy) "
42: B2 Line has trailing whitespace: "        Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps "
82: B2 Line has trailing whitespace: "        Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 "
83: B2 Line has trailing whitespace: "    83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> "
92: B2 Line has trailing whitespace: "    "
106: B2 Line has trailing whitespace: "    "
123: B2 Line has trailing whitespace: "    "
128: B2 Line has trailing whitespace: "    "
130: B2 Line has trailing whitespace: "        page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 "
135: B2 Line has trailing whitespace: "        raw: 0200000000000040 ffff888100042b40 dead000000000100 "
137: B2 Line has trailing whitespace: "        raw: 0000000000000000 0000000000100010 00000000f5000000 "
139: B2 Line has trailing whitespace: "        head: 0200000000000040 ffff888100042b40 dead000000000100 "
141: B2 Line has trailing whitespace: "        head: 0000000000000000 0000000000100010 00000000f5000000 "
143: B2 Line has trailing whitespace: "        head: 0200000000000001 ffffffffffffff81 00000000ffffffff "
145: B2 Line has trailing whitespace: "        head: 0000000000000000 0000000000000000 00000000ffffffff "
148: B2 Line has trailing whitespace: "    "


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-10-06 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 14:41 [PATCH] Bluetooth: msft: Lock failed probe cleanup against feature readers Cen Zhang
2026-10-06 15:31 ` 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=6ac51447.c02443da.c755a.558c@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 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.