From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yinghsu@chromium.org
Subject: RE: [v2] Bluetooth: Fix possible deadlock in rfcomm_sk_state_change
Date: Wed, 04 Jan 2023 07:36:12 -0800 (PST) [thread overview]
Message-ID: <63b59cec.020a0220.20d26.dae8@mx.google.com> (raw)
In-Reply-To: <20230104150642.v2.1.I1f29bb547a03e9adfe2e6754212f9d14a2e39c4b@changeid>
[-- Attachment #1: Type: text/plain, Size: 1420 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=708835
---Test result---
Test Summary:
CheckPatch PASS 1.16 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 32.55 seconds
CheckAllWarning PASS 35.19 seconds
CheckSparse PASS 40.03 seconds
CheckSmatch PASS 107.60 seconds
BuildKernel32 PASS 31.41 seconds
TestRunnerSetup PASS 447.97 seconds
TestRunner_l2cap-tester PASS 16.79 seconds
TestRunner_iso-tester PASS 17.57 seconds
TestRunner_bnep-tester PASS 5.89 seconds
TestRunner_mgmt-tester PASS 112.75 seconds
TestRunner_rfcomm-tester PASS 9.33 seconds
TestRunner_sco-tester PASS 8.45 seconds
TestRunner_ioctl-tester PASS 9.99 seconds
TestRunner_mesh-tester PASS 7.57 seconds
TestRunner_smp-tester PASS 8.36 seconds
TestRunner_userchan-tester PASS 6.05 seconds
IncrementalBuild PASS 29.68 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-04 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 15:07 [PATCH v2] Bluetooth: Fix possible deadlock in rfcomm_sk_state_change Ying Hsu
2023-01-04 15:36 ` bluez.test.bot [this message]
2023-01-04 22:21 ` Luiz Augusto von Dentz
2023-01-06 1:18 ` Saeed Mahameed
2023-01-06 19:44 ` Luiz Augusto von Dentz
2023-01-09 7:06 ` Ying Hsu
[not found] ` <CAAa9mD3hybWw0cZ9_p2ZWKQFFmPUvsj3efOB_j9VLd_4RgcmPA@mail.gmail.com>
2023-01-09 17:19 ` Luiz Augusto von Dentz
2023-01-10 2:15 ` Ying Hsu
2023-01-10 8:58 ` Saeed Mahameed
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=63b59cec.020a0220.20d26.dae8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yinghsu@chromium.org \
/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