From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw40880 [PATCH v10 2/5] bus/vmbus: add hyper-v virtual bus support
Date: Fri, 8 Jun 2018 19:00:41 +0200 (CEST) [thread overview]
Message-ID: <20180608170041.9584C1BA8E@dpdk.org> (raw)
In-Reply-To: <20180608165920.12228-3-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/40880
_coding style issues_
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#158: FILE: drivers/bus/vmbus/linux/vmbus_bus.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#185: FILE: drivers/bus/vmbus/linux/vmbus_bus.c:28:
+extern struct rte_vmbus_bus rte_vmbus_bus;
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#519: FILE: drivers/bus/vmbus/linux/vmbus_uio.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#1839: FILE: drivers/bus/vmbus/vmbus_bufring.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#2086: FILE: drivers/bus/vmbus/vmbus_channel.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#2498: FILE: drivers/bus/vmbus/vmbus_common.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#2523: FILE: drivers/bus/vmbus/vmbus_common.c:26:
+extern struct rte_vmbus_bus rte_vmbus_bus;
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#2790: FILE: drivers/bus/vmbus/vmbus_common_uio.c:1:
+/* SPDX-License-Identifier: BSD-3-Clause
total: 0 errors, 8 warnings, 2882 lines checked
parent reply other threads:[~2018-06-08 17:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180608165920.12228-3-stephen@networkplumber.org>]
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=20180608170041.9584C1BA8E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).