From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rasesh.mody@cavium.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, thomas@monjalon.net, Dept-EngDPDKDev@cavium.com
Subject: Re: [dpdk-dev] [PATCH v2] net/qede: move SPDX tags to source files
Date: Wed, 18 Jul 2018 11:32:34 +0100 [thread overview]
Message-ID: <575f418c-35ac-d3b6-943b-e85a136ce579@intel.com> (raw)
In-Reply-To: <1531532067-31551-1-git-send-email-rasesh.mody@cavium.com>
On 7/14/2018 2:34 AM, Rasesh Mody wrote:
> We were using LICENSE.qede_pmd to reference inclusion of SPDX licensing
> tag from all the source file. Remove the LICENSE.qede_pmd file and
> directly include SPDX tags in source files.
>
> Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-07-18 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 5:27 [dpdk-dev] [PATCH] " Rasesh Mody
2018-07-09 6:39 ` Hemant Agrawal
2018-07-10 15:56 ` Mody, Rasesh
2018-07-14 1:34 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2018-07-16 6:26 ` Hemant
2018-07-18 10:32 ` Ferruh Yigit [this message]
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=575f418c-35ac-d3b6-943b-e85a136ce579@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=rasesh.mody@cavium.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).