From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Subject: [dpdk-test-report] |WARNING| pw50219 [18/38] net/sfc/base: support different Tx descriptor sizes
Date: Thu, 7 Feb 2019 17:35:02 +0100 (CET) [thread overview]
Message-ID: <20190207163502.085AC1B5DA@dpdk.org> (raw)
In-Reply-To: <1549556983-10896-19-git-send-email-arybchenko@solarflare.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/50219
_coding style issues_
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#44: FILE: drivers/net/sfc/base/ef10_impl.h:22:
+#define EF10_TXQ_DESC_SIZE (sizeof (efx_qword_t))
CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around 'esmp == NULL'
#61: FILE: drivers/net/sfc/base/ef10_tx.c:46:
+ if ((esmp == NULL) ||
+ (EFSYS_MEM_SIZE(esmp) < efx_txq_size(enp, ndescs))) {
CHECK:CAMELCASE: Avoid CamelCase: <__checkReturn>
#100: FILE: drivers/net/sfc/base/efx.h:2661:
+extern __checkReturn size_t
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#101: FILE: drivers/net/sfc/base/efx.h:2662:
+efx_txq_size(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#106: FILE: drivers/net/sfc/base/efx.h:2667:
+efx_txq_nbufs(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#122: FILE: drivers/net/sfc/base/efx_tx.c:301:
+efx_txq_size(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#132: FILE: drivers/net/sfc/base/efx_tx.c:311:
+efx_txq_nbufs(
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#189: FILE: drivers/net/sfc/base/siena_impl.h:37:
+#define SIENA_TXQ_DESC_SIZE (sizeof (efx_qword_t))
total: 0 errors, 2 warnings, 6 checks, 125 lines checked
parent reply other threads:[~2019-02-07 16:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1549556983-10896-19-git-send-email-arybchenko@solarflare.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=20190207163502.085AC1B5DA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arybchenko@solarflare.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).