From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: net: Bluetooth: add TX timestamping for ISO/L2CAP/SCO
Date: Sun, 09 Feb 2025 03:28:22 -0800 (PST) [thread overview]
Message-ID: <67a89156.170a0220.299f78.562f@mx.google.com> (raw)
In-Reply-To: <71b88f509237bcce4139c152b3f624d7532047fd.1739097311.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2172 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=931989
---Test result---
Test Summary:
CheckPatch PENDING 0.33 seconds
GitLint PENDING 0.26 seconds
SubjectPrefix FAIL 0.57 seconds
BuildKernel PASS 23.88 seconds
CheckAllWarning PASS 26.68 seconds
CheckSparse WARNING 30.05 seconds
BuildKernel32 PASS 24.15 seconds
TestRunnerSetup PASS 423.29 seconds
TestRunner_l2cap-tester PASS 20.23 seconds
TestRunner_iso-tester PASS 27.56 seconds
TestRunner_bnep-tester PASS 4.76 seconds
TestRunner_mgmt-tester PASS 119.84 seconds
TestRunner_rfcomm-tester PASS 7.48 seconds
TestRunner_sco-tester PASS 9.31 seconds
TestRunner_ioctl-tester PASS 8.91 seconds
TestRunner_mesh-tester PASS 5.96 seconds
TestRunner_smp-tester PASS 6.86 seconds
TestRunner_userchan-tester PASS 4.97 seconds
IncrementalBuild PENDING 0.95 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
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):net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:147:35: warning: array of flexible structures
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-02-09 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 10:39 [PATCH v3 0/5] net: Bluetooth: add TX timestamping for ISO/L2CAP/SCO Pauli Virtanen
2025-02-09 10:39 ` [PATCH v3 1/5] net-timestamp: COMPLETION timestamp on packet tx completion Pauli Virtanen
2025-02-09 11:28 ` bluez.test.bot [this message]
2025-02-10 3:29 ` Willem de Bruijn
2025-02-10 17:50 ` Pauli Virtanen
2025-02-10 18:43 ` Willem de Bruijn
2025-02-11 21:34 ` Luiz Augusto von Dentz
2025-02-12 1:33 ` Willem de Bruijn
2025-02-15 12:43 ` Pauli Virtanen
2025-02-10 3:32 ` Jason Xing
2025-02-09 10:39 ` [PATCH v3 2/5] Bluetooth: add support for skb TX SND/COMPLETION timestamping Pauli Virtanen
2025-02-10 5:39 ` Jason Xing
2025-02-09 10:39 ` [PATCH v3 3/5] Bluetooth: ISO: add TX timestamping Pauli Virtanen
2025-02-10 5:19 ` Jason Xing
2025-02-10 18:33 ` Pauli Virtanen
2025-02-09 10:39 ` [PATCH v3 4/5] Bluetooth: L2CAP: " Pauli Virtanen
2025-02-09 10:39 ` [PATCH v3 5/5] Bluetooth: SCO: add TX timestamping socket-level mechanism Pauli Virtanen
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 19:06 [PATCH v5 1/5] net-timestamp: COMPLETION timestamp on packet tx completion Pauli Virtanen
2025-03-18 19:14 ` net: Bluetooth: add TX timestamping for ISO/L2CAP/SCO bluez.test.bot
2025-03-18 19:19 ` Luiz Augusto von Dentz
2025-03-18 21: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=67a89156.170a0220.299f78.562f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.