From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ori Kam <orika@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw62249 [PATCH v7 02/14] ethdev: add support for hairpin queue
Date: Mon, 4 Nov 2019 12:02:09 +0100 (CET) [thread overview]
Message-ID: <20191104110209.E187637B4@dpdk.org> (raw)
In-Reply-To: <1572479604-178752-3-git-send-email-orika@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/62249
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#131: FILE: lib/librte_ethdev/rte_ethdev.c:928:
+ "Can't start Rx hairpin queue %"PRIu16" of device with port_id=%"PRIu16"
",
WARNING:LONG_LINE: line over 90 characters
#145: FILE: lib/librte_ethdev/rte_ethdev.c:962:
+ "Can't stop Rx hairpin queue %"PRIu16" of device with port_id=%"PRIu16"
",
WARNING:LONG_LINE: line over 90 characters
#159: FILE: lib/librte_ethdev/rte_ethdev.c:1002:
+ "Can't start Tx hairpin queue %"PRIu16" of device with port_id=%"PRIu16"
",
WARNING:LONG_LINE: line over 90 characters
#173: FILE: lib/librte_ethdev/rte_ethdev.c:1034:
+ "Can't stop Tx hairpin queue %"PRIu16" of device with port_id=%"PRIu16"
",
WARNING:LONG_LINE: line over 90 characters
#386: FILE: lib/librte_ethdev/rte_ethdev.c:4395:
+ "Can't get hairpin Rx queue %"PRIu16" info of device with port_id=%"PRIu16"
",
WARNING:LONG_LINE: line over 90 characters
#400: FILE: lib/librte_ethdev/rte_ethdev.c:4426:
+ "Can't get hairpin Tx queue %"PRIu16" info of device with port_id=%"PRIu16"
",
total: 0 errors, 6 warnings, 692 lines checked
parent reply other threads:[~2019-11-04 11:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1572479604-178752-3-git-send-email-orika@mellanox.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=20191104110209.E187637B4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=orika@mellanox.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).