From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-test-report] |WARNING| pw24407 [PATCH RFC 1/4] vfio: refactor sockets into separate files
Date: Fri, 19 May 2017 18:40:10 +0200 (CEST) [thread overview]
Message-ID: <20170519164010.D562247CE@dpdk.org> (raw)
In-Reply-To: <1495211986-15177-2-git-send-email-anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/24407
_coding style issues_
ERROR:EXECUTE_PERMISSIONS: do not set execute permissions for source files
#38: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c
WARNING:TABSTOP: Statements should start on a tabstop
#105: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c:63:
+ do {\
ERROR:CODE_INDENT: code indent should use tabs where possible
#106: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c:64:
+^I (chdr).cmsg_len = CMSGLEN;\$
ERROR:CODE_INDENT: code indent should use tabs where possible
#107: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c:65:
+^I (chdr).cmsg_level = SOL_SOCKET;\$
ERROR:CODE_INDENT: code indent should use tabs where possible
#108: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c:66:
+^I (chdr).cmsg_type = SCM_RIGHTS;\$
ERROR:CODE_INDENT: code indent should use tabs where possible
#109: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c:67:
+^I memcpy((chdr).__cmsg_data, &(fd), sizeof(fd));\$
WARNING:TABSTOP: Statements should start on a tabstop
#110: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c:68:
+ } while (0)
ERROR:CODE_INDENT: code indent should use tabs where possible
#112: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.c:70:
+^I memcpy(&(fd), (chdr).__cmsg_data, sizeof(fd))$
ERROR:EXECUTE_PERMISSIONS: do not set execute permissions for source files
#345: FILE: lib/librte_eal/linuxapp/eal/eal_mp_socket.h
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#533: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.h:207:
+#define SOCKET_REQ_CONTAINER SOCKET_REQ_USER + 0
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#534: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.h:208:
+#define SOCKET_REQ_GROUP SOCKET_REQ_USER + 1
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#535: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.h:209:
+#define SOCKET_CLR_GROUP SOCKET_REQ_USER + 2
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#536: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.h:210:
+#define SOCKET_NO_FD SOCKET_REQ_USER + 3
total: 11 errors, 2 warnings, 820 lines checked
parent reply other threads:[~2017-05-19 16:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1495211986-15177-2-git-send-email-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=20170519164010.D562247CE@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).