From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Jan Viktorin <viktorin@rehivetech.com>, dev@dpdk.org
Cc: jerin.jacob@caviumnetworks.com, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH 4/6] test: use SPDX tag for RehiveTech copyright files
Date: Tue, 10 Apr 2018 09:47:25 +0530 [thread overview]
Message-ID: <7983ba91-c3ff-1ea7-8dd4-74fb74e566d6@nxp.com> (raw)
In-Reply-To: <20180409221558.3009-5-viktorin@rehivetech.com>
On 4/10/2018 3:45 AM, Jan Viktorin wrote:
> Replace the BSD license header with the SPDX tag for files
> with only an RehiveTech copyright on them.
>
> Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
> ---
> test/test/resource.c | 33 ++-------------------------------
> test/test/resource.h | 33 ++-------------------------------
> test/test/test_resource.c | 33 ++-------------------------------
> 3 files changed, 6 insertions(+), 93 deletions(-)
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
<snip>..
next prev parent reply other threads:[~2018-04-10 4:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 22:15 [dpdk-dev] [PATCH 0/6] Use SPDX identifier of RehiveTech code Jan Viktorin
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 [this message]
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=7983ba91-c3ff-1ea7-8dd4-74fb74e566d6@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.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 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).