From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: Bluetooth: mgmt: Fix limited discoverable off timeout
Date: Mon, 22 Jan 2024 10:03:45 -0800 (PST) [thread overview]
Message-ID: <65aeae01.050a0220.502c3.5805@mx.google.com> (raw)
In-Reply-To: <20240122165955.280126-1-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1428 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=818709
---Test result---
Test Summary:
CheckPatch PASS 43.26 seconds
GitLint PASS 40.68 seconds
SubjectPrefix PASS 39.07 seconds
BuildKernel PASS 27.86 seconds
CheckAllWarning PASS 38.74 seconds
CheckSparse PASS 76.42 seconds
CheckSmatch PASS 119.42 seconds
BuildKernel32 PASS 40.00 seconds
TestRunnerSetup PASS 437.18 seconds
TestRunner_l2cap-tester PASS 26.76 seconds
TestRunner_iso-tester PASS 47.64 seconds
TestRunner_bnep-tester PASS 7.90 seconds
TestRunner_mgmt-tester PASS 159.16 seconds
TestRunner_rfcomm-tester PASS 10.99 seconds
TestRunner_sco-tester PASS 14.43 seconds
TestRunner_ioctl-tester PASS 12.50 seconds
TestRunner_mesh-tester PASS 10.90 seconds
TestRunner_smp-tester PASS 23.59 seconds
TestRunner_userchan-tester PASS 7.29 seconds
IncrementalBuild PASS 29.75 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-01-22 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 16:59 [PATCH] Bluetooth: mgmt: Fix limited discoverable off timeout Frédéric Danis
2024-01-22 18:03 ` bluez.test.bot [this message]
2024-01-23 15:30 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 16:04 Frédéric Danis
2024-01-22 16:31 ` 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=65aeae01.050a0220.502c3.5805@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.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