DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK checkpatch and SPDX tags?
Date: Fri, 8 Jun 2018 10:15:11 -0700	[thread overview]
Message-ID: <20180608101511.567e4716@xeon-e3> (raw)

What ever happened to my patch to fix the DPDK checkpatch wrapper ignore fields?
Is the build bot using current version?

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

             reply	other threads:[~2018-06-08 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 17:15 Stephen Hemminger [this message]
2018-06-08 19:34 ` Thomas Monjalon

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=20180608101511.567e4716@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).