From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, suunj1331@gmail.com
Subject: RE: Bluetooth: Fix data-races in SCO/ISO connect paths
Date: Mon, 01 Jun 2026 05:49:18 -0700 (PDT) [thread overview]
Message-ID: <6a1d7fce.a9c3b6c1.259637.15c6@mx.google.com> (raw)
In-Reply-To: <20260601111908.232707-2-suunj1331@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1096 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/project/bluetooth/list/?series=1103971
---Test result---
Test Summary:
CheckPatch PASS 1.45 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 0.65 seconds
SubjectPrefix PASS 0.25 seconds
BuildKernel PASS 25.56 seconds
CheckAllWarning PASS 28.06 seconds
CheckSparse PASS 26.62 seconds
BuildKernel32 PASS 24.57 seconds
TestRunnerSetup PASS 524.16 seconds
TestRunner_iso-tester PASS 79.34 seconds
TestRunner_sco-tester PASS 32.06 seconds
IncrementalBuild PASS 26.22 seconds
https://github.com/bluez/bluetooth-next/pull/265
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-01 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 11:19 [PATCH v2 0/2] Bluetooth: Fix data-races in SCO/ISO connect paths SeungJu Cheon
2026-06-01 11:19 ` [PATCH v2 1/2] Bluetooth: ISO: Fix data-race on iso_pi fields in hci_get_route calls SeungJu Cheon
2026-06-01 12:49 ` bluez.test.bot [this message]
2026-06-01 11:19 ` [PATCH v2 2/2] Bluetooth: SCO: Fix data-race on sco_pi fields in sco_connect SeungJu Cheon
2026-06-02 17:20 ` [PATCH v2 0/2] Bluetooth: Fix data-races in SCO/ISO connect paths 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=6a1d7fce.a9c3b6c1.259637.15c6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=suunj1331@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