From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mmandlik@google.com
Subject: RE: [v12,1/4] Bluetooth: Add support for hci devcoredump
Date: Wed, 29 Mar 2023 23:36:26 -0700 (PDT) [thread overview]
Message-ID: <64252dea.c80a0220.2ab0f.051f@mx.google.com> (raw)
In-Reply-To: <20230329230447.v12.1.I9b4e4818bab450657b19cda3497d363c9baa616e@changeid>
[-- Attachment #1: Type: text/plain, Size: 2131 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=735223
---Test result---
Test Summary:
CheckPatch FAIL 5.20 seconds
GitLint PASS 1.33 seconds
SubjectPrefix PASS 0.49 seconds
BuildKernel PASS 32.04 seconds
CheckAllWarning PASS 34.89 seconds
CheckSparse PASS 40.08 seconds
CheckSmatch PASS 108.57 seconds
BuildKernel32 PASS 30.79 seconds
TestRunnerSetup PASS 438.85 seconds
TestRunner_l2cap-tester PASS 16.13 seconds
TestRunner_iso-tester PASS 16.03 seconds
TestRunner_bnep-tester PASS 5.28 seconds
TestRunner_mgmt-tester PASS 105.46 seconds
TestRunner_rfcomm-tester PASS 8.45 seconds
TestRunner_sco-tester PASS 7.76 seconds
TestRunner_ioctl-tester PASS 9.06 seconds
TestRunner_mesh-tester PASS 6.62 seconds
TestRunner_smp-tester PASS 7.68 seconds
TestRunner_userchan-tester PASS 5.49 seconds
IncrementalBuild PASS 45.71 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v12,1/4] Bluetooth: Add support for hci devcoredump
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#167:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 706 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/13193418.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-03-30 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 6:05 [PATCH v12 1/4] Bluetooth: Add support for hci devcoredump Manish Mandlik
2023-03-30 6:05 ` [PATCH v12 2/4] Bluetooth: Add vhci devcoredump support Manish Mandlik
2023-03-30 9:21 ` kernel test robot
2023-03-30 10:02 ` kernel test robot
2023-03-30 6:05 ` [PATCH v12 3/4] Bluetooth: btusb: Add btusb " Manish Mandlik
2023-03-30 6:05 ` [PATCH v12 4/4] Bluetooth: btintel: Add Intel " Manish Mandlik
2023-03-30 6:36 ` 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=64252dea.c80a0220.2ab0f.051f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mmandlik@google.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