From: Jan Viktorin <viktorin@rehivetech.com>
To: dev@dpdk.org
Cc: jerin.jacob@caviumnetworks.com,
Thomas Monjalon <thomas@monjalon.net>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Jan Viktorin <viktorin@rehivetech.com>
Subject: [dpdk-dev] [PATCH 0/6] Use SPDX identifier of RehiveTech code
Date: Tue, 10 Apr 2018 00:15:52 +0200 [thread overview]
Message-ID: <20180409221558.3009-1-viktorin@rehivetech.com> (raw)
Hi all,
I've updated all relevant code to SPDX license. The last commit
also updates the Cavium copyright, I've separated it for clarity
otherwise it can be squashed into 02.
Jan
Jan Viktorin (6):
mk: use SPDX tag for RehiveTech copyright files
lib: use SPDX tag for RehiveTech copyright files
drivers: use SPDX tag for RehiveTech copyright files
test: use SPDX tag for RehiveTech copyright files
config: use SPDX tag for RehiveTech copyright files
lib: use SPDX tag for Cavium & RehiveTech copyright files
config/defconfig_arm-armv7a-linuxapp-gcc | 31 ++------------------
drivers/bus/vdev/rte_bus_vdev.h | 32 ++------------------
drivers/bus/vdev/vdev.c | 32 ++------------------
lib/librte_eal/common/arch/arm/rte_cpuflags.c | 34 ++--------------------
.../common/include/arch/arm/rte_atomic.h | 32 ++------------------
.../common/include/arch/arm/rte_atomic_32.h | 32 ++------------------
.../common/include/arch/arm/rte_byteorder.h | 32 ++------------------
.../common/include/arch/arm/rte_cpuflags.h | 32 ++------------------
.../common/include/arch/arm/rte_cpuflags_32.h | 32 ++------------------
.../common/include/arch/arm/rte_cycles.h | 32 ++------------------
.../common/include/arch/arm/rte_cycles_32.h | 32 ++------------------
.../common/include/arch/arm/rte_memcpy.h | 32 ++------------------
.../common/include/arch/arm/rte_memcpy_32.h | 32 ++------------------
.../common/include/arch/arm/rte_prefetch.h | 32 ++------------------
.../common/include/arch/arm/rte_prefetch_32.h | 32 ++------------------
.../common/include/arch/arm/rte_spinlock.h | 32 ++------------------
mk/arch/arm/rte.vars.mk | 32 ++------------------
mk/machine/armv7a/rte.vars.mk | 31 ++------------------
test/test/resource.c | 33 ++-------------------
test/test/resource.h | 33 ++-------------------
test/test/test_resource.c | 33 ++-------------------
21 files changed, 43 insertions(+), 632 deletions(-)
--
2.16.2
next reply other threads:[~2018-04-09 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 22:15 Jan Viktorin [this message]
2018-04-09 22:15 ` [dpdk-dev] [PATCH 1/6] mk: use SPDX tag for RehiveTech copyright files Jan Viktorin
2018-04-10 4:10 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 2/6] lib: " Jan Viktorin
2018-04-10 4:15 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 3/6] drivers: " Jan Viktorin
2018-04-10 4:18 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 4/6] test: " Jan Viktorin
2018-04-10 4:17 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 5/6] config: " Jan Viktorin
2018-04-10 4:16 ` Hemant Agrawal
2018-04-09 22:15 ` [dpdk-dev] [PATCH 6/6] lib: use SPDX tag for Cavium & " Jan Viktorin
2018-04-10 0:43 ` Jerin Jacob
2018-04-10 23:02 ` [dpdk-dev] [PATCH 0/6] Use SPDX identifier of RehiveTech code 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=20180409221558.3009-1-viktorin@rehivetech.com \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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).