From: Shahaf Shuler <shahafs@mellanox.com>
To: thomas@monjalon.net, ferruh.yigit@intel.com
Cc: dev@dpdk.org, matan@mellanox.com
Subject: [dpdk-dev] [PATCH v2 5/9] net/vdev_netvsc: align SPDX Mellanox copyrights
Date: Tue, 20 Mar 2018 21:20:39 +0200 [thread overview]
Message-ID: <65634162f3b248a303aa24880fae4fec6e260a65.1521573303.git.shahafs@mellanox.com> (raw)
In-Reply-To: <cover.1521573302.git.shahafs@mellanox.com>
Aligning Mellanox SPDX copyrights to a single format.
Cc: matan@mellanox.com
Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
---
doc/guides/nics/vdev_netvsc.rst | 2 +-
drivers/net/vdev_netvsc/Makefile | 2 +-
drivers/net/vdev_netvsc/vdev_netvsc.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/guides/nics/vdev_netvsc.rst b/doc/guides/nics/vdev_netvsc.rst
index 55d130a3e..1c3084dda 100644
--- a/doc/guides/nics/vdev_netvsc.rst
+++ b/doc/guides/nics/vdev_netvsc.rst
@@ -1,6 +1,6 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright 2017 6WIND S.A.
- Copyright 2017 Mellanox Technologies, Ltd.
+ Copyright 2017 Mellanox Technologies, Ltd
VDEV_NETVSC driver
==================
diff --git a/drivers/net/vdev_netvsc/Makefile b/drivers/net/vdev_netvsc/Makefile
index 7be171375..690cb8f88 100644
--- a/drivers/net/vdev_netvsc/Makefile
+++ b/drivers/net/vdev_netvsc/Makefile
@@ -1,6 +1,6 @@
# SPDX-License-Identifier: BSD-3-Clause
# Copyright 2017 6WIND S.A.
-# Copyright 2017 Mellanox Technologies, Ltd.
+# Copyright 2017 Mellanox Technologies, Ltd
include $(RTE_SDK)/mk/rte.vars.mk
diff --git a/drivers/net/vdev_netvsc/vdev_netvsc.c b/drivers/net/vdev_netvsc/vdev_netvsc.c
index db0080a18..f7102d768 100644
--- a/drivers/net/vdev_netvsc/vdev_netvsc.c
+++ b/drivers/net/vdev_netvsc/vdev_netvsc.c
@@ -1,6 +1,6 @@
/* SPDX-License-Identifier: BSD-3-Clause
* Copyright 2017 6WIND S.A.
- * Copyright 2017 Mellanox Technologies, Ltd.
+ * Copyright 2017 Mellanox Technologies, Ltd
*/
#include <errno.h>
--
2.12.0
next prev parent reply other threads:[~2018-03-20 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 17:17 [dpdk-dev] [PATCH] net/mlx: align to SPDX format Shahaf Shuler
2018-03-20 17:25 ` Ferruh Yigit
2018-03-20 17:28 ` Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 0/9] align SPDX Mellanox copyrights Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 1/9] net/mlx: " Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 2/9] net/tap: " Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 3/9] app/testpmd: " Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 4/9] net/failsafe: " Shahaf Shuler
2018-03-20 19:20 ` Shahaf Shuler [this message]
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 6/9] eal: " Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 7/9] ethdev: " Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 8/9] net: " Shahaf Shuler
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 9/9] doc: " Shahaf Shuler
2018-03-22 9:18 ` [dpdk-dev] [PATCH v2 0/9] " Adrien Mazarguil
2018-04-10 23:08 ` 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=65634162f3b248a303aa24880fae4fec6e260a65.1521573303.git.shahafs@mellanox.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@mellanox.com \
--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).