From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: [RFC] Bluetooth: Convert MSFT filter HCI cmd to hci_sync
Date: Fri, 18 Nov 2022 21:02:08 -0800 (PST) [thread overview]
Message-ID: <63786350.020a0220.625b7.4cd8@mx.google.com> (raw)
In-Reply-To: <20221031220205.91975-1-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1257 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=690652
---Test result---
Test Summary:
CheckPatch PASS 0.60 seconds
GitLint PASS 0.29 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 33.72 seconds
BuildKernel32 PASS 30.16 seconds
TestRunnerSetup PASS 420.94 seconds
TestRunner_l2cap-tester PASS 15.68 seconds
TestRunner_iso-tester PASS 15.07 seconds
TestRunner_bnep-tester PASS 5.26 seconds
TestRunner_mgmt-tester PASS 103.94 seconds
TestRunner_rfcomm-tester PASS 9.08 seconds
TestRunner_sco-tester PASS 8.59 seconds
TestRunner_ioctl-tester PASS 9.86 seconds
TestRunner_mesh-tester PASS 6.69 seconds
TestRunner_smp-tester PASS 8.41 seconds
TestRunner_userchan-tester PASS 5.52 seconds
IncrementalBuild PASS 31.24 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-11-19 5:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 22:02 [RFC] Bluetooth: Convert MSFT filter HCI cmd to hci_sync Brian Gix
2022-10-31 22:05 ` Gix, Brian
2022-10-31 23:10 ` bluez.test.bot
2022-10-31 23:25 ` Luiz Augusto von Dentz
2022-11-01 15:39 ` Gix, Brian
2022-11-18 3:50 ` bluez.test.bot
2022-11-18 4:34 ` bluez.test.bot
2022-11-18 5:30 ` bluez.test.bot
2022-11-18 6:33 ` bluez.test.bot
2022-11-18 7:31 ` bluez.test.bot
2022-11-18 8:33 ` bluez.test.bot
2022-11-18 9:30 ` bluez.test.bot
2022-11-19 3:56 ` bluez.test.bot
2022-11-19 5:02 ` bluez.test.bot [this message]
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=63786350.020a0220.625b7.4cd8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=brian.gix@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox