From: Neil Horman <nhorman@tuxdriver.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] usertools: add missing SPDX identifier
Date: Mon, 9 Apr 2018 06:24:08 -0400 [thread overview]
Message-ID: <20180409102408.GA14747@hmswarspite.think-freely.org> (raw)
In-Reply-To: <1523264319-26429-4-git-send-email-hemant.agrawal@nxp.com>
On Mon, Apr 09, 2018 at 02:28:36PM +0530, Hemant Agrawal wrote:
> CC: nhorman@tuxdriver.com
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> usertools/dpdk-pmdinfo.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/usertools/dpdk-pmdinfo.py b/usertools/dpdk-pmdinfo.py
> index 46c1be0..03623d5 100755
> --- a/usertools/dpdk-pmdinfo.py
> +++ b/usertools/dpdk-pmdinfo.py
> @@ -1,4 +1,6 @@
> #!/usr/bin/env python
> +# SPDX-License-Identifier: BSD-3-Clause
> +# Copyright(c) 2016 Neil Horman <nhorman@tuxdriver.com>
>
> # -------------------------------------------------------------------------
> #
> --
> 2.7.4
>
>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
next prev parent reply other threads:[~2018-04-09 10:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 8:58 [PATCH] net/vmxnet3: change the SPDX tag style Hemant Agrawal
2018-04-09 8:58 ` [PATCH] eal: add missing SPDX identifiers Hemant Agrawal
2018-05-25 8:20 ` Thomas Monjalon
2018-04-09 8:58 ` [PATCH] test/crypto-perf: add missing SPDX identifier Hemant Agrawal
2018-04-17 15:08 ` De Lara Guarch, Pablo
2018-04-17 15:10 ` De Lara Guarch, Pablo
2018-04-09 8:58 ` [PATCH] usertools: " Hemant Agrawal
2018-04-09 10:24 ` Neil Horman [this message]
2018-04-10 23:50 ` Thomas Monjalon
2018-04-09 8:58 ` [PATCH] usertools: change to SPDX license identifier Hemant Agrawal
2018-04-09 9:07 ` Jerin Jacob
2018-04-10 23:50 ` Thomas Monjalon
2018-04-09 8:58 ` [PATCH] kernel: add missing " Hemant Agrawal
2018-04-09 8:58 ` [PATCH] pkg: change to " Hemant Agrawal
2018-05-25 8:22 ` Thomas Monjalon
2018-04-12 21:39 ` [PATCH] net/vmxnet3: change the SPDX tag style Yong Wang
2018-04-17 17:44 ` Ferruh Yigit
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=20180409102408.GA14747@hmswarspite.think-freely.org \
--to=nhorman@tuxdriver.com \
--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.