From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw56402 [PATCH v4 10/11] examples/qos_sched: add tc and queue config flexibility
Date: Fri, 12 Jul 2019 11:59:12 +0200 (CEST) [thread overview]
Message-ID: <20190712095912.7D44A1BDF1@dpdk.org> (raw)
In-Reply-To: <20190712095729.159767-11-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/56402
_coding style issues_
WARNING:LONG_LINE_COMMENT: line over 90 characters
#62: FILE: examples/qos_sched/app_thread.c:43:
+ (RTE_SCHED_TRAFFIC_CLASSES_PER_PIPE - 1) : *queue); /* Destination IP */
WARNING:LONG_LINE: line over 90 characters
#859: FILE: examples/qos_sched/stats.c:179:
+ subport_queue_id += port_params.n_pipes_per_subport * RTE_SCHED_QUEUES_PER_PIPE;
WARNING:LONG_LINE: line over 90 characters
#867: FILE: examples/qos_sched/stats.c:187:
+ queue_id = subport_queue_id + i * RTE_SCHED_QUEUES_PER_PIPE + tc;
WARNING:LONG_LINE: line over 90 characters
#874: FILE: examples/qos_sched/stats.c:194:
+ i * RTE_SCHED_QUEUES_PER_PIPE + tc + j;
WARNING:LONG_LINE: line over 90 characters
#886: FILE: examples/qos_sched/stats.c:206:
+ part_average / (port_params.n_pipes_per_subport) * RTE_SCHED_BE_QUEUES_PER_PIPE;
WARNING:LONG_LINE: line over 90 characters
#931: FILE: examples/qos_sched/stats.c:239:
+ subport_queue_id += port_params.n_pipes_per_subport * RTE_SCHED_QUEUES_PER_PIPE;
WARNING:LONG_LINE: line over 90 characters
#960: FILE: examples/qos_sched/stats.c:255:
+ average += part_average / (port_params.n_pipes_per_subport * RTE_SCHED_QUEUES_PER_PIPE);
WARNING:LONG_LINE: line over 90 characters
#1032: FILE: examples/qos_sched/stats.c:293:
+ printf("| %d | %11" PRIu32 " | %11" PRIu32 " | %11" PRIu32 " | %11" PRIu32 " | %11" PRIu32 " |
", i,
WARNING:LONG_LINE: line over 90 characters
#1112: FILE: examples/qos_sched/stats.c:336:
+ printf("| %d | %d | %11" PRIu32 " | %11" PRIu32 " | %11" PRIu32 " | %11" PRIu32 " | %11i |
", i, 0,
WARNING:LONG_LINE: line over 90 characters
#1113: FILE: examples/qos_sched/stats.c:337:
+ stats.n_pkts, stats.n_pkts_dropped, stats.n_bytes, stats.n_bytes_dropped, qlen);
WARNING:LONG_LINE: line over 90 characters
#1117: FILE: examples/qos_sched/stats.c:341:
+ rte_sched_queue_read_stats(port, queue_id + i + j, &stats, &qlen);
WARNING:LONG_LINE: line over 90 characters
#1118: FILE: examples/qos_sched/stats.c:342:
+ printf("| %d | %d | %11" PRIu32 " | %11" PRIu32 " | %11" PRIu32 " | %11" PRIu32 " | %11i |
", i, j,
WARNING:LONG_LINE: line over 90 characters
#1119: FILE: examples/qos_sched/stats.c:343:
+ stats.n_pkts, stats.n_pkts_dropped, stats.n_bytes, stats.n_bytes_dropped, qlen);
total: 0 errors, 13 warnings, 1042 lines checked
parent reply other threads:[~2019-07-12 9:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190712095729.159767-11-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=20190712095912.7D44A1BDF1@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).