automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Liang Ma <liang.j.ma@intel.com>
Subject: [dpdk-test-report] |WARNING| pw40815 [PATCH v1 1/2] lib/librte_power: traffic pattern aware power control
Date: Fri,  8 Jun 2018 16:18:55 +0200 (CEST)	[thread overview]
Message-ID: <20180608141855.ECFD91BA8F@dpdk.org> (raw)
In-Reply-To: <1528451833-3617-1-git-send-email-liang.j.ma@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/40815

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#31: 
how many cycles it costs to handle each packet and determining the frequency

WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#136: FILE: lib/librte_power/rte_empty_poll.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause

WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'poll_stats->thresh[poll_stats->cur_freq].threshold_percent'
#389: FILE: lib/librte_power/rte_empty_poll.c:254:
+		if (percent > poll_stats->thresh[poll_stats->cur_freq].
+				threshold_percent) {

WARNING:MULTILINE_DEREFERENCE: Avoid multiple line dereference - prefer 'poll_stats->thresh[poll_stats->cur_freq].threshold_percent'
#404: FILE: lib/librte_power/rte_empty_poll.c:269:
+		if (percent < poll_stats->thresh[poll_stats->cur_freq].
+				threshold_percent) {

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#418: FILE: lib/librte_power/rte_empty_poll.c:283:
+static int
+empty_poll_trainning(struct priority_worker *poll_stats,
+		uint32_t max_train_iter) {

total: 1 errors, 4 warnings, 682 lines checked

           reply	other threads:[~2018-06-08 14:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1528451833-3617-1-git-send-email-liang.j.ma@intel.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=20180608141855.ECFD91BA8F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=liang.j.ma@intel.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).