From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v3] Bluetooth: btintel: Set Per Platform Antenna Gain(PPAG)
Date: Sun, 05 Feb 2023 23:32:54 -0800 (PST) [thread overview]
Message-ID: <63e0ad26.170a0220.5b1d3.9c2e@mx.google.com> (raw)
In-Reply-To: <20230206065144.28322-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2196 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=719011
---Test result---
Test Summary:
CheckPatch FAIL 1.62 seconds
GitLint PASS 0.26 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 31.77 seconds
CheckAllWarning PASS 34.63 seconds
CheckSparse PASS 38.56 seconds
CheckSmatch PASS 107.45 seconds
BuildKernel32 PASS 30.17 seconds
TestRunnerSetup PASS 434.62 seconds
TestRunner_l2cap-tester PASS 16.45 seconds
TestRunner_iso-tester PASS 16.84 seconds
TestRunner_bnep-tester PASS 5.40 seconds
TestRunner_mgmt-tester PASS 108.59 seconds
TestRunner_rfcomm-tester PASS 8.62 seconds
TestRunner_sco-tester PASS 7.92 seconds
TestRunner_ioctl-tester PASS 9.25 seconds
TestRunner_mesh-tester PASS 6.83 seconds
TestRunner_smp-tester PASS 7.91 seconds
TestRunner_userchan-tester PASS 5.68 seconds
IncrementalBuild PASS 27.83 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3] Bluetooth: btintel: Set Per Platform Antenna Gain(PPAG)
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#92:
< HCI Command: Intel Configure Per Platform Antenna Gain (0x3f|0x0219) plen 12
total: 0 errors, 1 warnings, 165 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/13129360.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
next prev parent reply other threads:[~2023-02-06 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 6:51 [PATCH v3] Bluetooth: btintel: Set Per Platform Antenna Gain(PPAG) Kiran K
2023-02-06 7:32 ` bluez.test.bot [this message]
2023-02-06 22:00 ` 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=63e0ad26.170a0220.5b1d3.9c2e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kiran.k@intel.com \
--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.