From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 15013537245@163.com
Subject: RE: Bluetooth: hci_sync: fix BR/EDR wakeup bug
Date: Mon, 18 Dec 2023 03:00:27 -0800 (PST) [thread overview]
Message-ID: <6580264b.170a0220.27e61.44de@mx.google.com> (raw)
In-Reply-To: <20231218102417.474022-1-15013537245@163.com>
[-- Attachment #1: Type: text/plain, Size: 1422 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=810984
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint PASS 0.23 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 27.50 seconds
CheckAllWarning PASS 30.48 seconds
CheckSparse PASS 35.67 seconds
CheckSmatch PASS 98.12 seconds
BuildKernel32 PASS 26.65 seconds
TestRunnerSetup PASS 422.81 seconds
TestRunner_l2cap-tester PASS 22.82 seconds
TestRunner_iso-tester PASS 44.30 seconds
TestRunner_bnep-tester PASS 7.30 seconds
TestRunner_mgmt-tester PASS 160.21 seconds
TestRunner_rfcomm-tester PASS 10.54 seconds
TestRunner_sco-tester PASS 15.86 seconds
TestRunner_ioctl-tester PASS 11.74 seconds
TestRunner_mesh-tester PASS 8.62 seconds
TestRunner_smp-tester PASS 9.47 seconds
TestRunner_userchan-tester PASS 7.24 seconds
IncrementalBuild PASS 25.96 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-12-18 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 10:24 [PATCH] Bluetooth: hci_sync: fix BR/EDR wakeup bug 15013537245
2023-12-18 11:00 ` bluez.test.bot [this message]
2023-12-19 18:28 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-12-14 9:22 15013537245
2023-12-14 9:56 ` bluez.test.bot
2023-12-05 2:41 [PATCH] " 15013537245
2023-12-05 3:33 ` bluez.test.bot
2023-11-27 9:05 [PATCH] " 15013537245
2023-11-27 9:33 ` 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=6580264b.170a0220.27e61.44de@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=15013537245@163.com \
--cc=linux-bluetooth@vger.kernel.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 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.