From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Alex Kiselev <alex@therouter.net>
Subject: [dpdk-test-report] |WARNING| pw40092 [PATCH 2/2] librte_ip_frag: add mbuf counter
Date: Wed, 16 May 2018 13:04:28 +0200 (CEST) [thread overview]
Message-ID: <20180516110428.819B11B2B2@dpdk.org> (raw)
In-Reply-To: <20180516110424.C3F171B28D@dpdk.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/40092
_coding style issues_
ERROR:TRAILING_WHITESPACE: trailing whitespace
#47: FILE: lib/librte_ip_frag/ip_frag_common.h:35:
+struct rte_mbuf * ip_frag_process(struct rte_ip_frag_tbl *tbl, $
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#47: FILE: lib/librte_ip_frag/ip_frag_common.h:35:
+struct rte_mbuf * ip_frag_process(struct rte_ip_frag_tbl *tbl,
ERROR:TRAILING_WHITESPACE: trailing whitespace
#48: FILE: lib/librte_ip_frag/ip_frag_common.h:36:
+^Istruct ip_frag_pkt *fp, struct rte_ip_frag_death_row *dr, $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#58: FILE: lib/librte_ip_frag/ip_frag_common.h:94:
+ip_frag_free(struct rte_ip_frag_tbl *tbl, struct ip_frag_pkt *fp, $
ERROR:SPACING: space prohibited before that '--' (ctx:WxO)
#67: FILE: lib/librte_ip_frag/ip_frag_common.h:104:
+ tbl->nb_mbufs --;
^
ERROR:ELSE_AFTER_BRACE: else should follow close brace '}'
#136: FILE: lib/librte_ip_frag/ip_frag_internal.c:211:
}
+ else
ERROR:TRAILING_WHITESPACE: trailing whitespace
#162: FILE: lib/librte_ip_frag/rte_ip_frag.h:337:
+ * $
total: 7 errors, 0 warnings, 144 lines checked
parent reply other threads:[~2018-05-16 11:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180516110424.C3F171B28D@dpdk.org>]
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=20180516110428.819B11B2B2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=alex@therouter.net \
--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).