From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: [dpdk-test-report] |WARNING| pw24072 [PATCH RFC] service core concept header implementation
Date: Wed, 3 May 2017 13:30:24 +0200 (CEST) [thread overview]
Message-ID: <20170503113024.037D868C1@dpdk.org> (raw)
In-Reply-To: <1493810961-139469-2-git-send-email-harry.van.haaren@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/24072
_coding style issues_
WARNING:TYPO_SPELLING: 'seperate' may be misspelled - perhaps 'separate'?
#147: FILE: lib/librte_eal/common/include/rte_service.h:110:
+/** @internal - this will not be visible to application, defined in a seperate
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#149: FILE: lib/librte_eal/common/include/rte_service.h:112:
+ * to the actual function pointers - so hide them. */
ERROR:FUNCTION_WITHOUT_ARGS: Bad function definition - uint32_t rte_eal_service_get_count() should probably be uint32_t rte_eal_service_get_count(void)
#191: FILE: lib/librte_eal/common/include/rte_service.h:154:
+uint32_t rte_eal_service_get_count();
total: 1 errors, 2 warnings, 211 lines checked
parent reply other threads:[~2017-05-03 11:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1493810961-139469-2-git-send-email-harry.van.haaren@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=20170503113024.037D868C1@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=harry.van.haaren@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).