From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jasvinder Singh <jasvinder.singh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw56645 [PATCH v5 10/11] examples/qos_sched: add tc and queue config flexibility
Date: Wed, 17 Jul 2019 16:43:56 +0200 (CEST) [thread overview]
Message-ID: <20190717144356.9C4021BE17@dpdk.org> (raw)
In-Reply-To: <20190717144245.138876-11-jasvinder.singh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/56645
_coding style issues_
WARNING:LONG_LINE_COMMENT: line over 90 characters
#66: FILE: examples/qos_sched/app_thread.c:42:
+ pipe_queue = active_queues[(pdata[QUEUE_OFFSET] >> 8) % n_active_queues]; /* Destination IP */
WARNING:LONG_LINE: line over 90 characters
#880: 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
#888: 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
#895: FILE: examples/qos_sched/stats.c:194:
+ i * RTE_SCHED_QUEUES_PER_PIPE + tc + j;
WARNING:LONG_LINE: line over 90 characters
#907: 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
#952: 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
#981: 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
#1053: 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
#1133: 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
#1134: 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
#1138: 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
#1139: 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
#1140: 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, 1063 lines checked
parent reply other threads:[~2019-07-17 14:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190717144245.138876-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=20190717144356.9C4021BE17@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).