From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, peter.tsao@mediatek.com
Subject: RE: [v1] Bluetooth: btusb: Add support Mediatek MT7925
Date: Mon, 19 Jun 2023 05:43:08 -0700 (PDT) [thread overview]
Message-ID: <64904d5c.4a0a0220.85dae.7d07@mx.google.com> (raw)
In-Reply-To: <20230619120053.7780-1-peter.tsao@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 2339 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=758356
---Test result---
Test Summary:
CheckPatch FAIL 1.34 seconds
GitLint PASS 0.30 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 32.91 seconds
CheckAllWarning PASS 36.02 seconds
CheckSparse PASS 41.64 seconds
CheckSmatch PASS 111.39 seconds
BuildKernel32 PASS 32.09 seconds
TestRunnerSetup PASS 455.16 seconds
TestRunner_l2cap-tester PASS 17.26 seconds
TestRunner_iso-tester PASS 23.51 seconds
TestRunner_bnep-tester PASS 5.71 seconds
TestRunner_mgmt-tester PASS 117.37 seconds
TestRunner_rfcomm-tester PASS 9.18 seconds
TestRunner_sco-tester PASS 8.50 seconds
TestRunner_ioctl-tester PASS 9.86 seconds
TestRunner_mesh-tester PASS 7.18 seconds
TestRunner_smp-tester PASS 8.29 seconds
TestRunner_userchan-tester PASS 6.02 seconds
IncrementalBuild PASS 30.51 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v1] Bluetooth: btusb: Add support Mediatek MT7925
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#83:
Add Mediatek private data in hdev to record the device for handle MT7925 flow.
WARNING: 'infomation' may be misspelled - perhaps 'information'?
#86:
The infomation in /sys/kernel/debug/usb/devices about the MT7925U
^^^^^^^^^^
total: 0 errors, 2 warnings, 151 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/src/13284386.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-06-19 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 12:00 [PATCH v1] Bluetooth: btusb: Add support Mediatek MT7925 Peter Tsao
2023-06-19 12:43 ` bluez.test.bot [this message]
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=64904d5c.4a0a0220.85dae.7d07@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=peter.tsao@mediatek.com \
/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).