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: Fix advertising instance accesses without hdev->lock
Date: Thu, 19 Nov 2026 00:21:51 -0800 (PST)	[thread overview]
Message-ID: <6afeb19f.4b6e150d.159faa.fc28@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0245-v14-e37270232af59a877004-1@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.75 seconds
VerifyFixes                   PASS      0.07 seconds
VerifySignedoff               PASS      0.07 seconds
GitLint                       PASS      0.46 seconds
SubjectPrefix                 PASS      0.14 seconds
BuildKernel                   PASS      31.85 seconds
CheckAllWarning               PASS      35.19 seconds
CheckSparse                   PASS      38.30 seconds
BuildKernel32                 PASS      31.79 seconds
CheckKernelLLVM               PASS      33.26 seconds
TestRunnerSetup               PASS      758.96 seconds
TestRunner_l2cap-tester       PASS      14.93 seconds
TestRunner_iso-tester         PASS      15.04 seconds
TestRunner_bnep-tester        PASS      3.13 seconds
TestRunner_mgmt-tester        PASS      89.31 seconds
TestRunner_rfcomm-tester      PASS      4.48 seconds
TestRunner_sco-tester         PASS      5.59 seconds
TestRunner_ioctl-tester       PASS      4.63 seconds
TestRunner_mesh-tester        PASS      5.51 seconds
TestRunner_smp-tester         PASS      4.31 seconds
TestRunner_userchan-tester    PASS      3.19 seconds
TestRunner_6lowpan-tester     PASS      4.42 seconds
IncrementalBuild              PASS      31.75 seconds



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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-11-19  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  0:32 [PATCH v2 0/2] Bluetooth: Fix advertising instance accesses without hdev->lock Cen Zhang
2026-11-19  0:32 ` [PATCH v2 1/2] Bluetooth: hci_sync: Fix remaining advertising instance UAFs Cen Zhang
2026-11-19  8:21   ` bluez.test.bot [this message]
2026-11-19  0:32 ` [PATCH v2 2/2] Bluetooth: hci_sync: Use controller handles for periodic advertising Cen Zhang
  -- strict thread matches above, loose matches on Subject: below --
2026-10-30 14:27 [PATCH 1/2] Bluetooth: hci_sync: Fix remaining advertising instance UAFs Cen Zhang
2026-10-30 16:45 ` Bluetooth: Fix advertising instance accesses without hdev->lock bluez.test.bot

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=6afeb19f.4b6e150d.159faa.fc28@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