From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Radu Nicolau <radu.nicolau@intel.com>
Subject: [dpdk-test-report] |WARNING| pw98445 [PATCH 2/4] net/iavf: add iAVF IPsec inline crypto support
Date: Thu, 9 Sep 2021 16:33:17 +0200 (CEST) [thread overview]
Message-ID: <20210909143317.25BEE122D56@dpdk.org> (raw)
In-Reply-To: <20210909142428.750634-3-radu.nicolau@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/98445
_coding style issues_
WARNING:TYPO_SPELLING: 'acknowledgement' may be misspelled - perhaps 'acknowledgment'?
#65:
operations. IPsec Crypto requests receive an initial acknowledgement
WARNING:TYPO_SPELLING: 'metdata' may be misspelled - perhaps 'metadata'?
#3429: FILE: drivers/net/iavf/iavf_rxtx.c:2494:
+iavf_ipsec_crypto_get_pkt_metdata(const struct iavf_tx_queue *txq,
WARNING:TYPO_SPELLING: 'metdata' may be misspelled - perhaps 'metadata'?
#3533: FILE: drivers/net/iavf/iavf_rxtx.c:2548:
+ ipsec_md = iavf_ipsec_crypto_get_pkt_metdata(txq, mb);
WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#3580: FILE: drivers/net/iavf/iavf_rxtx.c:2581:
+ if (idx == 0)
CHECK:CAMELCASE: Avoid CamelCase: <PRIx16>
#3902: FILE: drivers/net/iavf/iavf_rxtx.h:317:
+ "QW0: 0x%04"PRIx16" %04"PRIx16" %04"PRIx16" %04"PRIx16", "
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#3902: FILE: drivers/net/iavf/iavf_rxtx.h:317:
+ "QW0: 0x%04"PRIx16" %04"PRIx16" %04"PRIx16" %04"PRIx16", "
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#3903: FILE: drivers/net/iavf/iavf_rxtx.h:318:
+ "QW1: 0x%04"PRIx16" %04"PRIx16" %04"PRIx16" %04"PRIx16"
",
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#4433: FILE: drivers/net/iavf/iavf_rxtx.h:1061:
+ printf("QW0: Buffer Address : 0x%016"PRIx64"
",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#4433: FILE: drivers/net/iavf/iavf_rxtx.h:1061:
+ printf("QW0: Buffer Address : 0x%016"PRIx64"
",
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#4514: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:366:
+ const __m128i ptype_mask = _mm_set_epi16(
CHECK:LOGICAL_CONTINUATIONS: Logical continuations should be on the previous line
#4590: FILE: drivers/net/iavf/iavf_vchnl.c:349:
+ if (msg_opc == VIRTCHNL_OP_INLINE_IPSEC_CRYPTO
+ && imsg->ipsec_opcode ==
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#4612: FILE: drivers/net/iavf/iavf_vchnl.c:365:
+ if (rte_atomic32_read(
total: 0 errors, 4 warnings, 8 checks, 4771 lines checked
Warning in drivers/net/iavf/iavf.h:
Using rte_atomicNN_xxx
parent reply other threads:[~2021-09-09 14:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210909142428.750634-3-radu.nicolau@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=20210909143317.25BEE122D56@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=radu.nicolau@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).