From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] add top level SPDX license identifier.
Date: Thu, 28 Nov 2019 16:16:15 +0100 [thread overview]
Message-ID: <3182516.DmcLIfpJrx@xps> (raw)
In-Reply-To: <20191128070538.27724-1-hemant.agrawal@nxp.com>
28/11/2019 08:05, Hemant Agrawal:
> This patch adds top level SPDX license identifiers for some of the dpdk
> source and scripts, where the copyright owners have not yet agreed to
> replace the full BSD-3 license plate.
>
> This patch also add SPDX license tag for some of files with no
> previous license plates. (DPDK is BSD-3)
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> app/test-pmd/flowgen.c | 7 ++-----
> app/test-pmd/macswap.c | 6 ++----
> app/test/test_compressdev_test_buffer.h | 2 ++
> app/test/test_timer_racecond.c | 8 +++-----
> devtools/cocci.sh | 3 +--
> .../test/trs_aesgcm_inline_crypto_fallback_defs.sh | 2 +-
> .../test/tun_aesgcm_inline_crypto_fallback_defs.sh | 2 +-
> examples/performance-thread/l3fwd-thread/test.sh | 1 +
> lib/librte_ethdev/rte_ethdev_pci.h | 6 ++----
> lib/librte_ethdev/rte_ethdev_vdev.h | 6 ++----
> 10 files changed, 17 insertions(+), 26 deletions(-)
If you don't mind, I would like to wait 20.02 for applying such patch.
I believe there is a chance to get some agreement for some of these files.
next prev parent reply other threads:[~2019-11-28 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 9:51 [dpdk-dev] [PATCH] add top level SPDX license identifier Hemant Agrawal
2019-11-28 7:05 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2019-11-28 15:16 ` Thomas Monjalon [this message]
2020-02-22 15:14 ` 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=3182516.DmcLIfpJrx@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.