automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Suanming Mou <suanmingm@nvidia.com>
Subject: |WARNING| pw126231 [RFC PATCH 4/5] crypto/mlx5: add queue pair setup
Date: Tue, 18 Apr 2023 11:25:09 +0200 (CEST)	[thread overview]
Message-ID: <20230418092509.61030121EF4@dpdk.org> (raw)
In-Reply-To: <20230418092325.2578712-5-suanmingm@nvidia.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#157: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2566:
+		if (attr->cd_master)

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#158: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2567:
+			MLX5_SET(qpc, qpc, cd_master, attr->cd_master);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#158: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2567:
+			MLX5_SET(qpc, qpc, cd_master, attr->cd_master);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#159: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2568:
+		if (attr->cd_slave_send)

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#160: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2569:
+			MLX5_SET(qpc, qpc, cd_slave_send, attr->cd_slave_send);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#160: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2569:
+			MLX5_SET(qpc, qpc, cd_slave_send, attr->cd_slave_send);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#161: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2570:
+		if (attr->cd_slave_recv)

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#162: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2571:
+			MLX5_SET(qpc, qpc, cd_slave_receive, attr->cd_slave_recv);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#162: FILE: drivers/common/mlx5/mlx5_devx_cmds.c:2571:
+			MLX5_SET(qpc, qpc, cd_slave_receive, attr->cd_slave_recv);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#174: FILE: drivers/common/mlx5/mlx5_devx_cmds.h:593:
+	uint32_t cd_master:1;

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#175: FILE: drivers/common/mlx5/mlx5_devx_cmds.h:594:
+	uint32_t cd_slave_send:1;

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#176: FILE: drivers/common/mlx5/mlx5_devx_cmds.h:595:
+	uint32_t cd_slave_recv:1;

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#442: FILE: drivers/crypto/mlx5/mlx5_crypto_gcm.c:259:
+	attr.cd_master = 1;

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#528: FILE: drivers/crypto/mlx5/mlx5_crypto_gcm.c:345:
+	qp_attr.cd_slave_send = 1;

total: 0 errors, 14 warnings, 397 lines checked

           reply	other threads:[~2023-04-18  9:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230418092325.2578712-5-suanmingm@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=20230418092509.61030121EF4@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=suanmingm@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).