From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Pallavi Kadam <pallavi.kadam@intel.com>
Subject: |WARNING| pw114546 [dpdk-kmods] windows/netuio: fix bar parsing
Date: Tue, 2 Aug 2022 21:13:48 +0200 (CEST) [thread overview]
Message-ID: <20220802191348.1B8AA120765@dpdk.org> (raw)
In-Reply-To: <20220802191058.1779-1-pallavi.kadam@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/114546
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#88: FILE: windows/netuio/netuio_dev.c:175:
+ BOOLEAN bar_done = FALSE;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#97: FILE: windows/netuio/netuio_dev.c:201:
+ if (curr_bar == 0 || ((prev_bar & PCI_TYPE_64BIT) && (bar_done))) {$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#97: FILE: windows/netuio/netuio_dev.c:201:
+ if (curr_bar == 0 || ((prev_bar & PCI_TYPE_64BIT) && (bar_done))) {$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#97: FILE: windows/netuio/netuio_dev.c:201:
+ if (curr_bar == 0 || ((prev_bar & PCI_TYPE_64BIT) && (bar_done))) {
+ bar_done = FALSE;
ERROR:CODE_INDENT: code indent should use tabs where possible
#98: FILE: windows/netuio/netuio_dev.c:202:
+ bar_done = FALSE;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#98: FILE: windows/netuio/netuio_dev.c:202:
+ bar_done = FALSE;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#106: FILE: windows/netuio/netuio_dev.c:224:
+ bar_done = TRUE;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#106: FILE: windows/netuio/netuio_dev.c:224:
+ bar_done = TRUE;$
total: 3 errors, 5 warnings, 23 lines checked
parent reply other threads:[~2022-08-02 19:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220802191058.1779-1-pallavi.kadam@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=20220802191348.1B8AA120765@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pallavi.kadam@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).