automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Vipin P R <vipinp@vmware.com>
Subject: |WARNING| pw122079 [PATCH] Intel iavf: Return in the case of ADD/DEL ETH address
Date: Sun, 15 Jan 2023 21:13:25 +0100 (CET)	[thread overview]
Message-ID: <20230115201326.0254D123659@dpdk.org> (raw)
In-Reply-To: <1673615963-21216-2-git-send-email-vipinp@vmware.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#104: 
In case of i40vf, VIRTCHNL_OP_DEL_ETH_ADDR and VIRTCHNL_OP_ADD_ETH_ADDR are unsupported.

WARNING:TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'?
#108: 
There is a retry logic of upto 200 times (2000 in iavf) with a delay of 10ms (1ms in iavf).

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#130: FILE: drivers/net/iavf/iavf_vchnl.c:371:
+    case VIRTCHNL_OP_ADD_ETH_ADDR:$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#131: FILE: drivers/net/iavf/iavf_vchnl.c:372:
+    case VIRTCHNL_OP_DEL_ETH_ADDR:$

ERROR:CODE_INDENT: code indent should use tabs where possible
#132: FILE: drivers/net/iavf/iavf_vchnl.c:373:
+        PMD_DRV_LOG(WARNING, "OP_{ADD/DEL}_ETH_ADDR unsupported");$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#132: FILE: drivers/net/iavf/iavf_vchnl.c:373:
+        PMD_DRV_LOG(WARNING, "OP_{ADD/DEL}_ETH_ADDR unsupported");$

ERROR:CODE_INDENT: code indent should use tabs where possible
#133: FILE: drivers/net/iavf/iavf_vchnl.c:374:
+        err = 0;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#133: FILE: drivers/net/iavf/iavf_vchnl.c:374:
+        err = 0;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#134: FILE: drivers/net/iavf/iavf_vchnl.c:375:
+        _clear_cmd(vf);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#134: FILE: drivers/net/iavf/iavf_vchnl.c:375:
+        _clear_cmd(vf);$

ERROR:CODE_INDENT: code indent should use tabs where possible
#135: FILE: drivers/net/iavf/iavf_vchnl.c:376:
+        break;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#135: FILE: drivers/net/iavf/iavf_vchnl.c:376:
+        break;$

total: 4 errors, 8 warnings, 0 checks, 14 lines checked
Vipin P R <vipinp@vmware.com> is unknown, please fix the commit message or update .mailmap.

      parent reply	other threads:[~2023-01-15 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1673615963-21216-2-git-send-email-vipinp@vmware.com>
2023-01-15 20:04 ` |SUCCESS| " qemudev
2023-01-15 20:08 ` qemudev
2023-01-15 20:13 ` checkpatch [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=20230115201326.0254D123659@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=vipinp@vmware.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;
as well as URLs for NNTP newsgroup(s).