From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: beilei.xing@intel.com
Subject: |WARNING| pw123112 [PATCH v7 13/19] common/idpf: add Rx and Tx data path
Date: Mon, 6 Feb 2023 07:16:03 +0100 (CET) [thread overview]
Message-ID: <20230206061603.95128121E50@dpdk.org> (raw)
In-Reply-To: <20230206054618.40975-14-beilei.xing@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/123112
_coding style issues_
ERROR:SPACING: space required after that ',' (ctx:VxB)
#124: FILE: drivers/common/idpf/idpf_common_logs.h:28:
+ RTE_FMT_HEAD(__VA_ARGS__,) "
", \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#126: FILE: drivers/common/idpf/idpf_common_logs.h:30:
+ RTE_FMT_TAIL(__VA_ARGS__,)))
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#136: FILE: drivers/common/idpf/idpf_common_logs.h:40:
+ RTE_FMT_HEAD(__VA_ARGS__,) "
", \
^
ERROR:SPACING: space required after that ',' (ctx:VxB)
#138: FILE: drivers/common/idpf/idpf_common_logs.h:42:
+ RTE_FMT_TAIL(__VA_ARGS__,)))
^
WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#1016: FILE: drivers/common/idpf/idpf_common_rxtx.c:1263:
+ if (nb_tx == 0)
total: 4 errors, 1 warnings, 0 checks, 2375 lines checked
parent reply other threads:[~2023-02-06 6:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230206054618.40975-14-beilei.xing@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=20230206061603.95128121E50@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=beilei.xing@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).