From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw28992 [PATCH v3 3/5] app/test-pmd: add CLI for shaper and wred profiles
Date: Thu, 21 Sep 2017 10:23:24 +0200 (CEST) [thread overview]
Message-ID: <20170921082324.1628D1B18C@dpdk.org> (raw)
In-Reply-To: <20170920095653.110750-3-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/28992
_coding style issues_
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#69: FILE: app/test-pmd/cmdline.c:14242:
+extern cmdline_parse_inst_t cmd_add_port_tm_node_shaper_profile;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#70: FILE: app/test-pmd/cmdline.c:14243:
+extern cmdline_parse_inst_t cmd_del_port_tm_node_shaper_profile;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#71: FILE: app/test-pmd/cmdline.c:14244:
+extern cmdline_parse_inst_t cmd_add_port_tm_node_shared_shaper;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#72: FILE: app/test-pmd/cmdline.c:14245:
+extern cmdline_parse_inst_t cmd_del_port_tm_node_shared_shaper;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#73: FILE: app/test-pmd/cmdline.c:14246:
+extern cmdline_parse_inst_t cmd_add_port_tm_node_wred_profile;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#74: FILE: app/test-pmd/cmdline.c:14247:
+extern cmdline_parse_inst_t cmd_del_port_tm_node_wred_profile;
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#75: FILE: app/test-pmd/cmdline.c:14248:
+extern cmdline_parse_inst_t cmd_set_port_tm_node_shaper_profile;
total: 0 errors, 7 warnings, 929 lines checked
parent reply other threads:[~2017-09-21 8:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170920095653.110750-3-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=20170921082324.1628D1B18C@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).