From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/5] Use SPDX tags on C files
Date: Wed, 20 Dec 2017 12:21:21 +0530 [thread overview]
Message-ID: <b97c6360-a029-463a-f9c1-9c1ab9d0e334@nxp.com> (raw)
In-Reply-To: <20171219143321.219543-1-bruce.richardson@intel.com>
On 12/19/2017 8:03 PM, Bruce Richardson wrote:
> This contains the output of a script run to replace the BSD License with
> SPDX tags on Intel copyright files. The script should only have modified
> files with a single, Intel copyright on them, and ignored all files that
> had multiple copyright lines. Due to variance in the headers used, not all
> files were updated automatically, 11 files were manually done in this set
> too. Any others missed can be updated in later sets once found.
>
SPDX tag is in 2nd line, first line of files is still "/*-" or it's
variances.
Linux uses the SPDX in the very first line as it will help in checkpatch
and other tools.
The proposed licenses/README states:
"DPDK uses first line of the file to be SPDX tag. In case of *#!*
scripts, SPDX tag can be placed in 2nd line of the file.
Also, do you plan to modify the "dual BSD/GPLv2" in separate patch set?
e.g icp_qat_fw.h?
> Bruce Richardson (5):
> app: use SPDX tags for Intel copyright files
> drivers: use SPDX tags for Intel copyright files
> examples: use SPDX tags for Intel copyright files
> lib: use SPDX tags for Intel copyright files
> test: use SPDX tags for Intel copyright files
next prev parent reply other threads:[~2017-12-20 6:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 14:33 Bruce Richardson
2017-12-19 14:33 ` [dpdk-dev] [PATCH 1/5] app: use SPDX tags for Intel copyright files Bruce Richardson
2017-12-19 14:33 ` [dpdk-dev] [PATCH 2/5] drivers: " Bruce Richardson
2017-12-19 14:33 ` [dpdk-dev] [PATCH 3/5] examples: " Bruce Richardson
2017-12-19 14:33 ` [dpdk-dev] [PATCH 4/5] lib: " Bruce Richardson
2017-12-19 14:33 ` [dpdk-dev] [PATCH 5/5] test: " Bruce Richardson
2017-12-20 6:51 ` Hemant Agrawal [this message]
2017-12-20 10:06 ` [dpdk-dev] [PATCH 0/5] Use SPDX tags on C files Bruce Richardson
2017-12-20 11:16 ` Bruce Richardson
2017-12-20 11:21 ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2017-12-20 11:21 ` [dpdk-dev] [PATCH v2 1/5] app: use SPDX tags for Intel copyright files Bruce Richardson
2017-12-20 11:21 ` [dpdk-dev] [PATCH v2 2/5] drivers: " Bruce Richardson
2017-12-20 11:21 ` [dpdk-dev] [PATCH v2 3/5] examples: " Bruce Richardson
2017-12-20 11:21 ` [dpdk-dev] [PATCH v2 4/5] lib: " Bruce Richardson
2017-12-20 11:22 ` [dpdk-dev] [PATCH v2 5/5] test: " Bruce Richardson
2018-01-04 21:14 ` [dpdk-dev] [PATCH v2 0/5] Use SPDX tags on C files 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=b97c6360-a029-463a-f9c1-9c1ab9d0e334@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).