From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw35897 [PATCH 19/37] ip_pipeline: add pipeline object
Date: Fri, 9 Mar 2018 19:26:23 +0100 (CET) [thread overview]
Message-ID: <20180309182623.D4C575F6E@dpdk.org> (raw)
In-Reply-To: <20180309182426.135278-20-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/35897
_coding style issues_
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#60: FILE: examples/ip_pipeline/cli.c:1000:
+ * ^Iperiod <timer_period_ms>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#61: FILE: examples/ip_pipeline/cli.c:1001:
+ * ^Ioffset_port_id <offset_port_id>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#62: FILE: examples/ip_pipeline/cli.c:1002:
+ * ^Icpu <cpu_id>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#120: FILE: examples/ip_pipeline/cli.c:1060:
+ * ^Ibsz <burst_size>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#121: FILE: examples/ip_pipeline/cli.c:1061:
+ * ^Ilink <link_name> rxq <queue_id>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#122: FILE: examples/ip_pipeline/cli.c:1062:
+ * ^I| swq <swq_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#123: FILE: examples/ip_pipeline/cli.c:1063:
+ * ^I| tmgr <tmgr_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#124: FILE: examples/ip_pipeline/cli.c:1064:
+ * ^I| tap <tap_name> mempool <mempool_name> mtu <mtu>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#125: FILE: examples/ip_pipeline/cli.c:1065:
+ * ^I| kni <kni_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#126: FILE: examples/ip_pipeline/cli.c:1066:
+ * ^I| source <source_name> mempool <mempool_name> file <file_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#316: FILE: examples/ip_pipeline/cli.c:1256:
+ * ^Ibsz <burst_size>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#317: FILE: examples/ip_pipeline/cli.c:1257:
+ * ^Ilink <link_name> txq <txq_id>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#318: FILE: examples/ip_pipeline/cli.c:1258:
+ * ^I| swq <swq_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#319: FILE: examples/ip_pipeline/cli.c:1259:
+ * ^I| tmgr <tmgr_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#320: FILE: examples/ip_pipeline/cli.c:1260:
+ * ^I| tap <tap_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#321: FILE: examples/ip_pipeline/cli.c:1261:
+ * ^I| kni <kni_name>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#322: FILE: examples/ip_pipeline/cli.c:1262:
+ * ^I| sink <sink_name> [file <file_name>]$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#462: FILE: examples/ip_pipeline/cli.c:1402:
+ * ^I^Iacl$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#463: FILE: examples/ip_pipeline/cli.c:1403:
+ * ^I^I^Iipv4 | ipv6$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#464: FILE: examples/ip_pipeline/cli.c:1404:
+ * ^I^I^Ioffset <ip_header_offset>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#465: FILE: examples/ip_pipeline/cli.c:1405:
+ * ^I^I^Isize <n_rules>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#466: FILE: examples/ip_pipeline/cli.c:1406:
+ * ^I^I| array$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#467: FILE: examples/ip_pipeline/cli.c:1407:
+ * ^I^I^Ioffset <key_offset>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#468: FILE: examples/ip_pipeline/cli.c:1408:
+ * ^I^I^Isize <n_keys>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#469: FILE: examples/ip_pipeline/cli.c:1409:
+ * ^I^I| hash$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#470: FILE: examples/ip_pipeline/cli.c:1410:
+ * ^I^I^Iext | lru$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#471: FILE: examples/ip_pipeline/cli.c:1411:
+ * ^I^I^Ikey <key_size>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#472: FILE: examples/ip_pipeline/cli.c:1412:
+ * ^I^I^Imask <key_mask>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#473: FILE: examples/ip_pipeline/cli.c:1413:
+ * ^I^I^Ioffset <key_offset>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#474: FILE: examples/ip_pipeline/cli.c:1414:
+ * ^I^I^Ibuckets <n_buckets>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#475: FILE: examples/ip_pipeline/cli.c:1415:
+ * ^I^I^Isize <n_keys>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#476: FILE: examples/ip_pipeline/cli.c:1416:
+ * ^I^I| lpm$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#477: FILE: examples/ip_pipeline/cli.c:1417:
+ * ^I^I^Iipv4 | ipv6$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#478: FILE: examples/ip_pipeline/cli.c:1418:
+ * ^I^I^Ioffset <ip_header_offset>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#479: FILE: examples/ip_pipeline/cli.c:1419:
+ * ^I^I^Isize <n_rules>$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#480: FILE: examples/ip_pipeline/cli.c:1420:
+ * ^I^I| stub$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#481: FILE: examples/ip_pipeline/cli.c:1421:
+ * ^Iaction <action_profile_name>$
total: 0 errors, 37 warnings, 2041 lines checked
parent reply other threads:[~2018-03-09 18:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180309182426.135278-20-jasvinder.singh@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=20180309182623.D4C575F6E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jasvinder.singh@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).