From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, linux@weissschuh.net
Subject: RE: HID: remove some unneeded exported symbols from hid.h
Date: Wed, 21 Dec 2022 21:59:21 -0800 (PST) [thread overview]
Message-ID: <63a3f239.ca0a0220.3874e.2e54@mx.google.com> (raw)
In-Reply-To: <20221222-hid-v1-1-f4a6c35487a5@weissschuh.net>
[-- Attachment #1: Type: text/plain, Size: 1913 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=706392
---Test result---
Test Summary:
CheckPatch PASS 6.97 seconds
GitLint PASS 2.49 seconds
SubjectPrefix FAIL 0.98 seconds
BuildKernel PASS 38.63 seconds
CheckAllWarning PASS 41.68 seconds
CheckSparse PASS 47.37 seconds
BuildKernel32 PASS 37.00 seconds
TestRunnerSetup PASS 522.93 seconds
TestRunner_l2cap-tester PASS 18.46 seconds
TestRunner_iso-tester PASS 20.10 seconds
TestRunner_bnep-tester PASS 6.85 seconds
TestRunner_mgmt-tester PASS 125.54 seconds
TestRunner_rfcomm-tester PASS 10.65 seconds
TestRunner_sco-tester PASS 9.85 seconds
TestRunner_ioctl-tester PASS 11.63 seconds
TestRunner_mesh-tester PASS 8.59 seconds
TestRunner_smp-tester PASS 9.65 seconds
TestRunner_userchan-tester PASS 7.27 seconds
IncrementalBuild PASS 76.47 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-12-22 5:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 5:10 [PATCH 0/8] HID: remove some unneeded exported symbols from hid.h Thomas Weißschuh
2022-12-22 5:10 ` [PATCH 1/8] HID: letsketch: Use hid_is_usb() Thomas Weißschuh
2022-12-22 5:59 ` bluez.test.bot [this message]
2022-12-22 5:10 ` [PATCH 2/8] HID: usbhid: Make hid_is_usb() non-inline Thomas Weißschuh
2022-12-22 21:12 ` Benjamin Tissoires
2022-12-22 21:37 ` Thomas Weißschuh
2022-12-23 7:56 ` Benjamin Tissoires
2022-12-22 5:10 ` [PATCH 3/8] HID: Remove unused function hid_is_using_ll_driver() Thomas Weißschuh
2022-12-22 5:10 ` [PATCH 4/8] HID: Unexport struct usb_hid_driver Thomas Weißschuh
2022-12-22 5:10 ` [PATCH 5/8] HID: Unexport struct uhid_hid_driver Thomas Weißschuh
2022-12-22 5:10 ` [PATCH 6/8] HID: Unexport struct hidp_hid_driver Thomas Weißschuh
2022-12-22 5:10 ` [PATCH 7/8] HID: Unexport struct i2c_hid_ll_driver Thomas Weißschuh
2022-12-22 5:10 ` [PATCH 8/8] HID: Make lowlevel driver structs const Thomas Weißschuh
2022-12-22 15:27 ` [PATCH 0/8] HID: remove some unneeded exported symbols from hid.h David Rheinsberg
2023-01-09 8:39 ` Hans de Goede
2023-01-17 12:45 ` Jiri Kosina
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=63a3f239.ca0a0220.3874e.2e54@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux@weissschuh.net \
/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