From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Richael Zhuang <richael.zhuang@arm.com>
Subject: [dpdk-test-report] |WARNING| pw90589 [PATCH v1 2/2] test/power: fix a bug in cpufreq autotest
Date: Tue, 6 Apr 2021 05:42:50 +0200 (CEST) [thread overview]
Message-ID: <20210406034251.033AE120D42@dpdk.org> (raw)
In-Reply-To: <20210406034110.55790-1-richael.zhuang@arm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/90589
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#175:
check_power_turbo() to continue if rte_power_turbo_status(TEST_POWER_LCORE_ID)!=1
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#200: FILE: app/test/test_power_cpufreq.c:392:
+ if (rte_power_turbo_status(TEST_POWER_LCORE_ID) != 1) {$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (7, 15)
#200: FILE: app/test/test_power_cpufreq.c:392:
+ if (rte_power_turbo_status(TEST_POWER_LCORE_ID) != 1) {
printf("Turbo not available on lcore %u, skipping test
",
total: 0 errors, 3 warnings, 8 lines checked
parent reply other threads:[~2021-04-06 3:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210406034110.55790-1-richael.zhuang@arm.com>]
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=20210406034251.033AE120D42@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=richael.zhuang@arm.com \
--cc=test-report@dpdk.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 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).