From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-test-report] |WARNING| pw32468 [PATCH RFC v2 06/23] eal: make malloc a doubly-linked list
Date: Tue, 19 Dec 2017 12:15:42 +0100 (CET) [thread overview]
Message-ID: <20171219111542.440021B267@dpdk.org> (raw)
In-Reply-To: <ee393950b6b2038a9d98b210bb8fd46c2174804a.1513681966.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/32468
_coding style issues_
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#157: FILE: lib/librte_eal/common/malloc_elem.c:190:
+static void __rte_unused
+remove_elem(struct malloc_elem *elem) {
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#176: FILE: lib/librte_eal/common/malloc_elem.c:209:
+static int
+next_elem_is_adjacent(struct malloc_elem *elem) {
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#181: FILE: lib/librte_eal/common/malloc_elem.c:214:
+static int
+prev_elem_is_adjacent(struct malloc_elem *elem) {
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#215: FILE: lib/librte_eal/common/malloc_elem.c:352:
+static struct malloc_elem *
+elem_join_adjacent_free(struct malloc_elem *elem) {
ERROR:SPACING: space required before the open brace '{'
#222: FILE: lib/librte_eal/common/malloc_elem.c:359:
+ next_elem_is_adjacent(elem)){
total: 5 errors, 0 warnings, 322 lines checked
parent reply other threads:[~2017-12-19 11:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ee393950b6b2038a9d98b210bb8fd46c2174804a.1513681966.git.anatoly.burakov@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=20171219111542.440021B267@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anatoly.burakov@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).