From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Soumyadeep Hore <soumyadeep.hore@intel.com>
Subject: |WARNING| pw140357 [PATCH 01/25] common/idpf: added NVME CPF specific code with defines
Date: Tue, 28 May 2024 10:11:06 +0200 (CEST) [thread overview]
Message-ID: <20240528081106.59DE412367B@dpdk.org> (raw)
In-Reply-To: <20240528072839.867100-2-soumyadeep.hore@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140357
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#149: FILE: drivers/common/idpf/base/idpf_controlq.c:249:
+ struct idpf_ctlq_create_info *q_info, struct idpf_ctlq_info **ctlq)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#149: FILE: drivers/common/idpf/base/idpf_controlq.c:249:
+ struct idpf_ctlq_create_info *q_info, struct idpf_ctlq_info **ctlq)$
ERROR:TRAILING_WHITESPACE: trailing whitespace
#164: FILE: drivers/common/idpf/base/idpf_controlq.c:267:
+#endif^I$
ERROR:CODE_INDENT: code indent should use tabs where possible
#173: FILE: drivers/common/idpf/base/idpf_controlq.c:422:
+^I^I struct idpf_ctlq_msg *msg_status[], bool force)$
ERROR:CODE_INDENT: code indent should use tabs where possible
#182: FILE: drivers/common/idpf/base/idpf_controlq.c:493:
+^I^I struct idpf_ctlq_msg *msg_status[])$
ERROR:CODE_INDENT: code indent should use tabs where possible
#203: FILE: drivers/common/idpf/base/idpf_controlq_api.h:163:
+ struct idpf_ctlq_create_info *q_info, struct idpf_ctlq_info **ctlq);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#203: FILE: drivers/common/idpf/base/idpf_controlq_api.h:163:
+ struct idpf_ctlq_create_info *q_info, struct idpf_ctlq_info **ctlq);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#216: FILE: drivers/common/idpf/base/idpf_controlq_api.h:194:
+^I^I struct idpf_ctlq_msg *msg_status[]);$
total: 6 errors, 2 warnings, 120 lines checked
parent reply other threads:[~2024-05-28 8:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240528072839.867100-2-soumyadeep.hore@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=20240528081106.59DE412367B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=soumyadeep.hore@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).