From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hongbo Liu <cnliuhb@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw39562 [PATCH] examples/ip_pipeline: Support quitting CLI connection
Date: Wed, 9 May 2018 13:35:14 +0200 (CEST) [thread overview]
Message-ID: <20180509113514.0CB001B28E@dpdk.org> (raw)
In-Reply-To: <CAATCt2SMYfQ7TmGdE5pCDy_3oiEaQrK+iw7-qE=vTSuH_dOcFA@mail.gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/39562
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#31: FILE: examples/ip_pipeline/conn.c:225:
+ if (!strncmp(conn->buf, "quit", strlen("quit")))$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (7, 15)
#31: FILE: examples/ip_pipeline/conn.c:225:
+ if (!strncmp(conn->buf, "quit", strlen("quit")))
+ return -2;
ERROR:CODE_INDENT: code indent should use tabs where possible
#32: FILE: examples/ip_pipeline/conn.c:226:
+ return -2;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#32: FILE: examples/ip_pipeline/conn.c:226:
+ return -2;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#41: FILE: examples/ip_pipeline/conn.c:321:
+ if (status_data == -2 || event.events & (EPOLLRDHUP | EPOLLERR |$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (7, 16)
#41: FILE: examples/ip_pipeline/conn.c:321:
+ if (status_data == -2 || event.events & (EPOLLRDHUP | EPOLLERR |
[...]
status_control = control_event_handle(conn, fd_client);
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#42: FILE: examples/ip_pipeline/conn.c:321:
EPOLLHUP))
total: 2 errors, 5 warnings, 16 lines checked
parent reply other threads:[~2018-05-09 11:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAATCt2SMYfQ7TmGdE5pCDy_3oiEaQrK+iw7-qE=vTSuH_dOcFA@mail.gmail.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=20180509113514.0CB001B28E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=cnliuhb@gmail.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).