From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Bluetooth: ISO: Match QoS adv handle with BIG handle
Date: Tue, 03 Oct 2023 08:42:21 -0700 (PDT) [thread overview]
Message-ID: <651c365d.170a0220.d327d.3bcd@mx.google.com> (raw)
In-Reply-To: <20231003143739.2925-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1427 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=789623
---Test result---
Test Summary:
CheckPatch PASS 0.64 seconds
GitLint PASS 0.26 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 41.21 seconds
CheckAllWarning PASS 44.77 seconds
CheckSparse PASS 51.08 seconds
CheckSmatch PASS 135.75 seconds
BuildKernel32 PASS 40.17 seconds
TestRunnerSetup PASS 602.36 seconds
TestRunner_l2cap-tester PASS 36.77 seconds
TestRunner_iso-tester PASS 61.80 seconds
TestRunner_bnep-tester PASS 13.83 seconds
TestRunner_mgmt-tester PASS 252.90 seconds
TestRunner_rfcomm-tester PASS 19.04 seconds
TestRunner_sco-tester PASS 22.40 seconds
TestRunner_ioctl-tester PASS 21.64 seconds
TestRunner_mesh-tester PASS 15.99 seconds
TestRunner_smp-tester PASS 17.23 seconds
TestRunner_userchan-tester PASS 13.50 seconds
IncrementalBuild PASS 37.36 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-10-03 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 14:37 [PATCH 0/1] Bluetooth: ISO: Match QoS adv handle with BIG handle Iulia Tanasescu
2023-10-03 14:37 ` [PATCH 1/1] " Iulia Tanasescu
2023-10-03 15:42 ` bluez.test.bot [this message]
2023-10-03 17:10 ` [PATCH 0/1] " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 15:37 [PATCH 1/1] " Iulia Tanasescu
2023-09-29 16:39 ` 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=651c365d.170a0220.d327d.3bcd@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.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;
as well as URLs for NNTP newsgroup(s).