From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yinghsu@chromium.org
Subject: RE: [RESEND] Bluetooth: Fix deadlock in vhci_send_frame
Date: Thu, 09 Nov 2023 18:09:19 -0800 (PST) [thread overview]
Message-ID: <654d90cf.050a0220.5f2d2.23a6@mx.google.com> (raw)
In-Reply-To: <20231110014605.2068231-1-yinghsu@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1423 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=800102
---Test result---
Test Summary:
CheckPatch PASS 1.72 seconds
GitLint PASS 0.48 seconds
SubjectPrefix PASS 0.29 seconds
BuildKernel PASS 26.98 seconds
CheckAllWarning PASS 29.80 seconds
CheckSparse PASS 34.96 seconds
CheckSmatch PASS 97.68 seconds
BuildKernel32 PASS 26.29 seconds
TestRunnerSetup PASS 410.70 seconds
TestRunner_l2cap-tester PASS 22.77 seconds
TestRunner_iso-tester PASS 41.80 seconds
TestRunner_bnep-tester PASS 6.88 seconds
TestRunner_mgmt-tester PASS 169.80 seconds
TestRunner_rfcomm-tester PASS 10.89 seconds
TestRunner_sco-tester PASS 14.49 seconds
TestRunner_ioctl-tester PASS 12.42 seconds
TestRunner_mesh-tester PASS 8.79 seconds
TestRunner_smp-tester PASS 10.53 seconds
TestRunner_userchan-tester PASS 7.24 seconds
IncrementalBuild PASS 25.39 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-11-10 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 1:46 [PATCH RESEND] Bluetooth: Fix deadlock in vhci_send_frame Ying Hsu
2023-11-10 2:09 ` bluez.test.bot [this message]
2023-11-13 3:52 ` Ying Hsu
2023-11-13 4:13 ` Luiz Augusto von Dentz
2023-11-17 16:20 ` 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=654d90cf.050a0220.5f2d2.23a6@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