From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-test-report] |WARNING| pw29422 [PATCH v6 1/4] librte_flow_classify: add librte_flow_classify library
Date: Fri, 29 Sep 2017 11:19:54 +0200 (CEST) [thread overview]
Message-ID: <20170929091954.220BF1B22C@dpdk.org> (raw)
In-Reply-To: <1506676737-23900-2-git-send-email-bernard.iremonger@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/29422
_coding style issues_
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#70: FILE: MAINTAINERS:681:
+M: Bernard Iremonger <bernard.iremonger@intel.com>
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#71: FILE: MAINTAINERS:682:
+F: lib/librte_flow_classify/
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#72: FILE: MAINTAINERS:683:
+F: test/test/test_flow_classify*
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#73: FILE: MAINTAINERS:684:
+F: examples/flow_classify/
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#74: FILE: MAINTAINERS:685:
+F: doc/guides/sample_app_ug/flow_classify.rst
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#75: FILE: MAINTAINERS:686:
+F: doc/guides/prog_guide/flow_classify_lib.rst
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 16)
#1071: FILE: lib/librte_flow_classify/rte_flow_classify_parse.c:184:
+ while (item->type == RTE_FLOW_ITEM_TYPE_VOID) {\
+ index++; \
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 16)
#1080: FILE: lib/librte_flow_classify/rte_flow_classify_parse.c:193:
+ while (act->type == RTE_FLOW_ACTION_TYPE_VOID) {\
+ index++; \
total: 0 errors, 8 warnings, 1417 lines checked
parent reply other threads:[~2017-09-29 9:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1506676737-23900-2-git-send-email-bernard.iremonger@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=20170929091954.220BF1B22C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bernard.iremonger@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).