From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, qwe.aldo@gmail.com
Subject: RE: [v2] Bluetooth: mgmt: fix race in read_unconf_index_list()
Date: Tue, 15 Sep 2026 10:43:56 -0700 (PDT) [thread overview]
Message-ID: <6aa983dc.d84cfa41.20622f.52b2@mx.google.com> (raw)
In-Reply-To: <20260915155952.3104711-1-qwe.aldo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1403 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/1165728/
---Test result---
Test Summary:
CheckPatch PASS 0.74 seconds
VerifyFixes PASS 0.12 seconds
VerifySignedoff PASS 0.12 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 29.77 seconds
CheckAllWarning PASS 33.94 seconds
CheckSparse PASS 37.81 seconds
BuildKernel32 PASS 29.75 seconds
CheckKernelLLVM PASS 35.40 seconds
TestRunnerSetup PASS 818.19 seconds
TestRunner_mgmt-tester FAIL 9.09 seconds
TestRunner_mesh-tester FAIL 7.86 seconds
IncrementalBuild PASS 28.25 seconds
Details
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
No test result found
https://github.com/bluez/bluetooth-next/pull/773
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-15 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 15:59 [PATCH v2] Bluetooth: mgmt: fix race in read_unconf_index_list() Aldo Ariel Panzardo
2026-09-15 17:43 ` bluez.test.bot [this message]
2026-09-16 18:00 ` 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=6aa983dc.d84cfa41.20622f.52b2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=qwe.aldo@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.