From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: Bluetooth: btusb: Fix quirks table naming
Date: Tue, 22 Aug 2023 04:04:45 -0700 (PDT) [thread overview]
Message-ID: <64e4964d.170a0220.2a563.05b3@mx.google.com> (raw)
In-Reply-To: <20230822102033.1169580-1-hadess@hadess.net>
[-- 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=778167
---Test result---
Test Summary:
CheckPatch PASS 0.54 seconds
GitLint PASS 0.23 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 42.21 seconds
CheckAllWarning PASS 40.29 seconds
CheckSparse PASS 44.94 seconds
CheckSmatch PASS 129.05 seconds
BuildKernel32 PASS 34.84 seconds
TestRunnerSetup PASS 557.30 seconds
TestRunner_l2cap-tester PASS 33.48 seconds
TestRunner_iso-tester PASS 77.29 seconds
TestRunner_bnep-tester PASS 13.25 seconds
TestRunner_mgmt-tester PASS 248.29 seconds
TestRunner_rfcomm-tester PASS 19.17 seconds
TestRunner_sco-tester PASS 25.49 seconds
TestRunner_ioctl-tester PASS 24.16 seconds
TestRunner_mesh-tester PASS 15.32 seconds
TestRunner_smp-tester PASS 16.72 seconds
TestRunner_userchan-tester PASS 14.04 seconds
IncrementalBuild PASS 34.63 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-08-22 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 10:20 [PATCH] Bluetooth: btusb: Fix quirks table naming Bastien Nocera
2023-08-22 10:41 ` Paul Menzel
2023-08-22 11:43 ` Bastien Nocera
2023-08-22 11:04 ` bluez.test.bot [this message]
2023-08-23 23:50 ` patchwork-bot+bluetooth
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=64e4964d.170a0220.2a563.05b3@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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.