From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rami Rosen <rami.rosen@intel.com>
Subject: [dpdk-test-report] |WARNING| pw37488 [PATCH v5 1/3] ether: support runtime queue setup
Date: Fri, 6 Apr 2018 21:42:49 +0200 (CEST) [thread overview]
Message-ID: <20180406194249.08C841CA35@dpdk.org> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F95319D7A0@HASMSX110.ger.corp.intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/37488
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#25:
Cc: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#119: FILE: lib/librte_ether/rte_ethdev.c:1600:
[Rami Rosen] Shouldn't it be here: dev->data->tx_queue_state[...] instead of:
ERROR:TRAILING_WHITESPACE: trailing whitespace
#136: FILE: lib/librte_ether/rte_ethdev.h:984:
+#define DEV_RUNTIME_RX_QUEUE_SETUP 0x00000001 /**< Deferred setup rx $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#137: FILE: lib/librte_ether/rte_ethdev.h:985:
+queue */ #define DEV_RUNTIME_TX_QUEUE_SETUP 0x00000002 /**< Deferred $
WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#137: FILE: lib/librte_ether/rte_ethdev.h:985:
+#define DEV_RUNTIME_RX_QUEUE_SETUP 0x00000001 /**< Deferred setup rx
+queue */ #define DEV_RUNTIME_TX_QUEUE_SETUP 0x00000002 /**< Deferred
WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#138: FILE: lib/librte_ether/rte_ethdev.h:986:
+queue */ #define DEV_RUNTIME_TX_QUEUE_SETUP 0x00000002 /**< Deferred
+setup tx queue */
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#138: FILE: lib/librte_ether/rte_ethdev.h:986:
+setup tx queue */
total: 3 errors, 4 warnings, 80 lines checked
parent reply other threads:[~2018-04-06 19:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9B0331B6EBBD0E4684FBFAEDA55776F95319D7A0@HASMSX110.ger.corp.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=20180406194249.08C841CA35@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rami.rosen@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).