[dpdk-test-report] |WARNING| pw90586 [PATCH] test/power: fix several bugs in cpufreq autotest
checkpatch at dpdk.org
checkpatch at dpdk.org
Tue Apr 6 04:57:40 CEST 2021
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/90586
_coding style issues_
ERROR:GERRIT_CHANGE_ID: Remove Gerrit Change-Id's before submitting upstream
#185:
Change-Id: I3b0266415a2b655d58294a3f51a6051bc1e5fc7f
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#218: FILE: app/test/test_power_cpufreq.c:51:
+ sleep(1);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#230: FILE: app/test/test_power_cpufreq.c:74:
+ * Ex: if cur_freq=1396789 then freq_conv=1400000$
ERROR:CODE_INDENT: code indent should use tabs where possible
#231: FILE: app/test/test_power_cpufreq.c:75:
+ * Ex: if cur_freq=800030 then freq_conv=800000$
ERROR:CODE_INDENT: code indent should use tabs where possible
#232: FILE: app/test/test_power_cpufreq.c:76:
+ */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#233: FILE: app/test/test_power_cpufreq.c:77:
+ unsigned int freq_conv = 0;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#234: FILE: app/test/test_power_cpufreq.c:78:
+ freq_conv = (cur_freq + TEST_FREQ_ROUNDING_DELTA)$
ERROR:CODE_INDENT: code indent should use tabs where possible
#235: FILE: app/test/test_power_cpufreq.c:79:
+ / TEST_ROUND_FREQ_TO_N_100000;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#235: FILE: app/test/test_power_cpufreq.c:79:
+ / TEST_ROUND_FREQ_TO_N_100000;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#236: FILE: app/test/test_power_cpufreq.c:80:
+ freq_conv = freq_conv * TEST_ROUND_FREQ_TO_N_100000;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#238: FILE: app/test/test_power_cpufreq.c:82:
+ ret = (freqs[idx] == freq_conv ? 0 : -1);$
total: 5 errors, 6 warnings, 37 lines checked
More information about the test-report
mailing list