From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, olivier.matz@6wind.com,
ferruh.yigit@intel.com,
Scott Branden <scott.branden@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/bnxt: convert to SPDX license tag
Date: Tue, 3 Apr 2018 11:59:20 +0530 [thread overview]
Message-ID: <d8e6d554-a98c-101d-f4be-7b8a4c5f5256@nxp.com> (raw)
In-Reply-To: <20180402223432.63032-1-ajit.khaparde@broadcom.com>
On 4/3/2018 4:04 AM, Ajit Khaparde wrote:
> From: Scott Branden <scott.branden@broadcom.com>
>
> Update the license header on bnxt files to be the standard
> BSD-3-Clause license used for the rest of DPDK,
> bring the files in compliance with the DPDK licensing policy.
>
> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> --
> v1->v2: modify first line of SPDX identifer according to review comment
> v2->v3: reformat the header to remove leading spaces as per review comment
>
>
<snip>...
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
next prev parent reply other threads:[~2018-04-03 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 19:07 [dpdk-dev] [PATCH] " Ajit Khaparde
2018-03-26 7:28 ` Hemant Agrawal
[not found] ` <3f4ea1f2-023e-46f8-96e2-e7380ed5f3c2@broadcom.com>
2018-03-27 6:51 ` Hemant Agrawal
2018-03-29 16:40 ` [dpdk-dev] [PATCH v2] " Ajit Khaparde
2018-03-30 10:35 ` Ferruh Yigit
2018-03-30 18:10 ` Scott Branden
2018-03-31 21:08 ` Ferruh Yigit
2018-04-02 18:57 ` Scott Branden
2018-04-02 22:34 ` [dpdk-dev] [PATCH v3] " Ajit Khaparde
2018-04-03 6:29 ` Hemant Agrawal [this message]
2018-04-05 14:40 ` 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=d8e6d554-a98c-101d-f4be-7b8a4c5f5256@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=scott.branden@broadcom.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).