From: Shahaf Shuler <shahafs@mellanox.com>
To: thomas@monjalon.net, ferruh.yigit@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/9] align SPDX Mellanox copyrights
Date: Tue, 20 Mar 2018 21:20:34 +0200 [thread overview]
Message-ID: <cover.1521573302.git.shahafs@mellanox.com> (raw)
In-Reply-To: <20180320171716.74448-1-shahafs@mellanox.com>
This series is to align the format of the copyright in Mellanox related files.
On v2:
- remove completely the BSD licence from mlx PMD docs
- add more patches to align files not under drivers/net/mlx*
Shahaf Shuler (9):
net/mlx: align SPDX Mellanox copyrights
net/tap: align SPDX Mellanox copyrights
app/testpmd: align SPDX Mellanox copyrights
net/failsafe: align SPDX Mellanox copyrights
net/vdev_netvsc: align SPDX Mellanox copyrights
eal: align SPDX Mellanox copyrights
ethdev: align SPDX Mellanox copyrights
net: align SPDX Mellanox copyrights
doc: align SPDX Mellanox copyrights
app/test-pmd/cmdline_flow.c | 2 +-
doc/guides/linux_gsg/linux_drivers.rst | 2 +-
doc/guides/nics/mlx4.rst | 30 ++-----------------
doc/guides/nics/mlx5.rst | 30 ++-----------------
doc/guides/nics/vdev_netvsc.rst | 2 +-
drivers/net/failsafe/failsafe.c | 2 +-
drivers/net/failsafe/failsafe_args.c | 2 +-
drivers/net/failsafe/failsafe_eal.c | 2 +-
drivers/net/failsafe/failsafe_ether.c | 2 +-
drivers/net/failsafe/failsafe_flow.c | 2 +-
drivers/net/failsafe/failsafe_intr.c | 2 +-
drivers/net/failsafe/failsafe_ops.c | 2 +-
drivers/net/failsafe/failsafe_private.h | 2 +-
drivers/net/failsafe/failsafe_rxtx.c | 2 +-
drivers/net/mlx4/Makefile | 31 ++------------------
drivers/net/mlx4/mlx4.c | 2 +-
drivers/net/mlx4/mlx4.h | 2 +-
drivers/net/mlx4/mlx4_ethdev.c | 2 +-
drivers/net/mlx4/mlx4_flow.c | 2 +-
drivers/net/mlx4/mlx4_flow.h | 2 +-
drivers/net/mlx4/mlx4_glue.c | 2 +-
drivers/net/mlx4/mlx4_glue.h | 2 +-
drivers/net/mlx4/mlx4_intr.c | 2 +-
drivers/net/mlx4/mlx4_mr.c | 2 +-
drivers/net/mlx4/mlx4_prm.h | 2 +-
drivers/net/mlx4/mlx4_rxq.c | 2 +-
drivers/net/mlx4/mlx4_rxtx.c | 2 +-
drivers/net/mlx4/mlx4_rxtx.h | 2 +-
drivers/net/mlx4/mlx4_txq.c | 2 +-
drivers/net/mlx4/mlx4_utils.c | 2 +-
drivers/net/mlx4/mlx4_utils.h | 2 +-
drivers/net/mlx5/Makefile | 31 ++------------------
drivers/net/mlx5/mlx5.c | 2 +-
drivers/net/mlx5/mlx5.h | 2 +-
drivers/net/mlx5/mlx5_defs.h | 2 +-
drivers/net/mlx5/mlx5_ethdev.c | 2 +-
drivers/net/mlx5/mlx5_flow.c | 2 +-
drivers/net/mlx5/mlx5_glue.c | 2 +-
drivers/net/mlx5/mlx5_glue.h | 2 +-
drivers/net/mlx5/mlx5_mac.c | 2 +-
drivers/net/mlx5/mlx5_mr.c | 2 +-
drivers/net/mlx5/mlx5_prm.h | 2 +-
drivers/net/mlx5/mlx5_rss.c | 2 +-
drivers/net/mlx5/mlx5_rxmode.c | 2 +-
drivers/net/mlx5/mlx5_rxq.c | 2 +-
drivers/net/mlx5/mlx5_rxtx.c | 2 +-
drivers/net/mlx5/mlx5_rxtx.h | 2 +-
drivers/net/mlx5/mlx5_rxtx_vec.c | 2 +-
drivers/net/mlx5/mlx5_rxtx_vec.h | 2 +-
drivers/net/mlx5/mlx5_rxtx_vec_neon.h | 2 +-
drivers/net/mlx5/mlx5_rxtx_vec_sse.h | 2 +-
drivers/net/mlx5/mlx5_socket.c | 1 +
drivers/net/mlx5/mlx5_stats.c | 2 +-
drivers/net/mlx5/mlx5_trigger.c | 2 +-
drivers/net/mlx5/mlx5_txq.c | 2 +-
drivers/net/mlx5/mlx5_utils.h | 2 +-
drivers/net/mlx5/mlx5_vlan.c | 2 +-
drivers/net/tap/rte_eth_tap.h | 2 +-
drivers/net/tap/tap_bpf.h | 2 +-
drivers/net/tap/tap_bpf_api.c | 2 +-
drivers/net/tap/tap_bpf_insns.h | 2 +-
drivers/net/tap/tap_bpf_program.c | 2 +-
drivers/net/tap/tap_flow.c | 2 +-
drivers/net/tap/tap_flow.h | 2 +-
drivers/net/tap/tap_intr.c | 2 +-
drivers/net/tap/tap_netlink.c | 2 +-
drivers/net/tap/tap_netlink.h | 2 +-
drivers/net/tap/tap_rss.h | 2 +-
drivers/net/tap/tap_tcmsgs.c | 2 +-
drivers/net/tap/tap_tcmsgs.h | 2 +-
drivers/net/vdev_netvsc/Makefile | 2 +-
drivers/net/vdev_netvsc/vdev_netvsc.c | 2 +-
lib/librte_eal/common/arch/arm/rte_hypervisor.c | 2 +-
.../common/arch/ppc_64/rte_hypervisor.c | 2 +-
lib/librte_eal/common/arch/x86/rte_hypervisor.c | 2 +-
lib/librte_eal/common/eal_common_hypervisor.c | 2 +-
lib/librte_eal/common/include/rte_hypervisor.h | 2 +-
lib/librte_ether/rte_flow.c | 2 +-
lib/librte_ether/rte_flow.h | 2 +-
lib/librte_ether/rte_flow_driver.h | 2 +-
lib/librte_net/rte_esp.h | 2 +-
81 files changed, 85 insertions(+), 190 deletions(-)
--
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 ` Shahaf Shuler [this message]
2018-03-20 19:20 ` [dpdk-dev] [PATCH v2 1/9] net/mlx: align SPDX Mellanox copyrights 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 ` [dpdk-dev] [PATCH v2 5/9] net/vdev_netvsc: " Shahaf Shuler
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=cover.1521573302.git.shahafs@mellanox.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).