From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync
Date: Thu, 17 Aug 2023 00:35:55 -0700 (PDT) [thread overview]
Message-ID: <64ddcddb.920a0220.604a4.30be@mx.google.com> (raw)
In-Reply-To: <20230817064427.3647-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1831 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=776876
---Test result---
Test Summary:
CheckPatch PASS 1.57 seconds
GitLint PASS 0.28 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 32.76 seconds
CheckAllWarning PASS 35.72 seconds
CheckSparse WARNING 40.23 seconds
CheckSmatch WARNING 113.18 seconds
BuildKernel32 PASS 31.03 seconds
TestRunnerSetup PASS 478.51 seconds
TestRunner_l2cap-tester PASS 27.42 seconds
TestRunner_iso-tester PASS 48.76 seconds
TestRunner_bnep-tester PASS 11.03 seconds
TestRunner_mgmt-tester PASS 220.60 seconds
TestRunner_rfcomm-tester PASS 16.08 seconds
TestRunner_sco-tester PASS 19.13 seconds
TestRunner_ioctl-tester PASS 18.04 seconds
TestRunner_mesh-tester PASS 13.44 seconds
TestRunner_smp-tester PASS 14.34 seconds
TestRunner_userchan-tester PASS 11.23 seconds
IncrementalBuild PASS 30.12 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-08-17 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 6:44 [PATCH v3 0/1] Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync Iulia Tanasescu
2023-08-17 6:44 ` [PATCH v3 1/1] " Iulia Tanasescu
2023-08-17 7:35 ` bluez.test.bot [this message]
2023-08-17 20:26 ` Pauli Virtanen
2023-08-17 21:39 ` Luiz Augusto von Dentz
2023-08-18 11:10 ` Iulia Tanasescu
2023-08-17 19:50 ` [PATCH v3 0/1] " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-08-16 15:00 [PATCH v2 1/1] " Iulia Tanasescu
2023-08-16 15:37 ` bluez.test.bot
2023-08-02 14:36 [PATCH 1/1] " Iulia Tanasescu
2023-08-02 15:37 ` 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=64ddcddb.920a0220.604a4.30be@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 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.