From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fady Bader <fady@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw71134 [PATCH 3/3] eal/windows: librte_net build on Windows
Date: Wed, 10 Jun 2020 13:24:44 +0200 (CEST) [thread overview]
Message-ID: <20200610112444.443A12C5E@dpdk.org> (raw)
In-Reply-To: <20200610112326.18576-4-fady@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/71134
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#93: FILE: lib/librte_eal/windows/include/netinet/in.h:2:
+/* SPDX-License-Identifier: BSD-3-Clause
++* Copyright 2020 Mellanox Technologies, Ltd */
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#93: FILE: lib/librte_eal/windows/include/netinet/in.h:2:
++* Copyright 2020 Mellanox Technologies, Ltd */
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#113: FILE: lib/librte_eal/windows/include/netinet/in.h:22:
+#define IPPROTO_SCTP 132 ^I/* Stream Control Transmission Protocol */$
WARNING:MISSING_EOF_NEWLINE: adding a line without newline at end of file
#114: FILE: lib/librte_eal/windows/include/netinet/in.h:23:
+#endif
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#123: FILE: lib/librte_eal/windows/include/netinet/ip.h:2:
+* Copyright 2020 Mellanox Technologies, Ltd */
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#123: FILE: lib/librte_eal/windows/include/netinet/ip.h:2:
+/* SPDX-License-Identifier: BSD-3-Clause
+* Copyright 2020 Mellanox Technologies, Ltd */
WARNING:MISSING_EOF_NEWLINE: adding a line without newline at end of file
#130: FILE: lib/librte_eal/windows/include/netinet/ip.h:9:
+#endif
total: 0 errors, 7 warnings, 51 lines checked
parent reply other threads:[~2020-06-10 11:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200610112326.18576-4-fady@mellanox.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=20200610112444.443A12C5E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=fady@mellanox.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).