From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [DNM,v3] Bluetooth: doc: test patch - DO NOT MERGE
Date: Thu, 17 Nov 2022 20:17:34 -0800 (PST) [thread overview]
Message-ID: <6377075e.620a0220.21e26.3be8@mx.google.com> (raw)
In-Reply-To: <20221116052716.57521-1-hj.tedd.an@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1260 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=695798
---Test result---
Test Summary:
CheckPatch PASS 0.52 seconds
GitLint PASS 0.26 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 40.50 seconds
BuildKernel32 PASS 36.69 seconds
TestRunnerSetup PASS 504.44 seconds
TestRunner_l2cap-tester PASS 17.83 seconds
TestRunner_iso-tester PASS 18.51 seconds
TestRunner_bnep-tester PASS 6.54 seconds
TestRunner_mgmt-tester PASS 120.17 seconds
TestRunner_rfcomm-tester PASS 10.78 seconds
TestRunner_sco-tester PASS 10.24 seconds
TestRunner_ioctl-tester PASS 11.72 seconds
TestRunner_mesh-tester PASS 8.15 seconds
TestRunner_smp-tester PASS 9.88 seconds
TestRunner_userchan-tester PASS 6.76 seconds
IncrementalBuild PASS 37.77 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-18 4:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 5:27 [DNM PATCH v3] Bluetooth: doc: test patch - DO NOT MERGE Tedd Ho-Jeong An
2022-11-16 6:08 ` [DNM,v3] " bluez.test.bot
2022-11-18 2:48 ` bluez.test.bot
2022-11-18 4:17 ` bluez.test.bot [this message]
2022-11-18 5:07 ` bluez.test.bot
2022-11-18 5:56 ` bluez.test.bot
2022-11-18 6:34 ` bluez.test.bot
2022-11-18 7:34 ` bluez.test.bot
2022-11-18 8:34 ` bluez.test.bot
2022-11-18 9:33 ` bluez.test.bot
2022-11-19 5:32 ` 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=6377075e.620a0220.21e26.3be8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hj.tedd.an@gmail.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