automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Michael Baum <michaelba@nvidia.com>
Subject: |WARNING| pw107910 [PATCH 20.11 3/5] net/mlx5: fix MPRQ stride devargs adjustment
Date: Mon, 21 Feb 2022 20:31:29 +0100 (CET)	[thread overview]
Message-ID: <20220221193129.6984F12336A@dpdk.org> (raw)
In-Reply-To: <20220221192918.2455579-4-michaelba@nvidia.com>

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

_coding style issues_


ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: bad o ("04e76d0eb77c163ff")'
#120: 
[ upstream commit 34776af600df4475799ad8004e76d0eb77c163ff ]

WARNING:TYPO_SPELLING: 'unsupport' may be misspelled - perhaps 'unsupported'?
#305: FILE: drivers/net/mlx5/mlx5_rxq.c:1425:
+		goto unsupport;

WARNING:TYPO_SPELLING: 'unsupport' may be misspelled - perhaps 'unsupported'?
#332: FILE: drivers/net/mlx5/mlx5_rxq.c:1452:
+			goto unsupport;

WARNING:TYPO_SPELLING: 'unsupport' may be misspelled - perhaps 'unsupported'?
#348: FILE: drivers/net/mlx5/mlx5_rxq.c:1468:
+		goto unsupport;

WARNING:TYPO_SPELLING: 'unsupport' may be misspelled - perhaps 'unsupported'?
#355: FILE: drivers/net/mlx5/mlx5_rxq.c:1475:
+		goto unsupport;

WARNING:TYPO_SPELLING: 'unsupport' may be misspelled - perhaps 'unsupported'?
#362: FILE: drivers/net/mlx5/mlx5_rxq.c:1482:
+unsupport:

total: 1 errors, 5 warnings, 0 checks, 352 lines checked

           reply	other threads:[~2022-02-21 19:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220221192918.2455579-4-michaelba@nvidia.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=20220221193129.6984F12336A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=michaelba@nvidia.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).