From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw72881 [PATCH v4 15/51] net/bnxt: add HCAPI interface support
Date: Fri, 3 Jul 2020 01:31:48 +0200 (CEST) [thread overview]
Message-ID: <20200702233148.95F871DA3F@dpdk.org> (raw)
In-Reply-To: <20200702232838.92817-16-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/72881
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'mask' - possible side-effects?
#511: FILE: drivers/net/bnxt/hcapi/hcapi_cfa_defs.h:26:
+#define __CFA_ALIGN_MASK(x, mask) (((x) + (mask)) & ~(mask))
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#561: FILE: drivers/net/bnxt/hcapi/hcapi_cfa_defs.h:76:
+ HCAPI_CFA_HWOPS_ADD, /**< For operations which require more than simple
+ * writes to HW, this operation is used. The
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#569: FILE: drivers/net/bnxt/hcapi/hcapi_cfa_defs.h:84:
+ HCAPI_CFA_HWOPS_DEL, /**< This issues operations to clear the hardware.
+ * This operation is used in conjunction
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'crc' - possible side-effects?
#1215: FILE: drivers/net/bnxt/hcapi/hcapi_cfa_p4.c:52:
+#define ucrc32(ch, crc) (crc32tbl[((crc) ^ (ch)) & 0xff] ^ ((crc) >> 8))
WARNING:LONG_LINE: line over 90 characters
#2089: FILE: drivers/net/bnxt/tf_core/tf_em.c:387:
+ mask = tf_em_get_key_mask(tbl_scope_cb->em_ctx_info[parms->dir].em_tables[TF_KEY0_TABLE].num_entries);
total: 0 errors, 3 warnings, 2 checks, 2228 lines checked
parent reply other threads:[~2020-07-02 23:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200702232838.92817-16-ajit.khaparde@broadcom.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=20200702233148.95F871DA3F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ajit.khaparde@broadcom.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).