From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Olivier MATZ <olivier.matz@6wind.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>, <dev@dpdk.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Subject: Re: [dpdk-dev] [PATCH] net: update licence for network headers
Date: Fri, 15 Dec 2017 16:24:07 +0530 [thread overview]
Message-ID: <20232357-08fc-c55e-53e0-a9bf5c3e359b@nxp.com> (raw)
In-Reply-To: <3574356.e36fbgbura@xps>
On 12/14/2017 6:28 PM, Thomas Monjalon wrote:
> 14/12/2017 12:33, Hemant Agrawal:
>> Thomas,
>> Before I rework,
>> What is your opinion w.r.t tooling in DPDK w.r.t SPDX.
>>
>> I saw a patch for checkpatch in Linux, which will also check for SPDX
>> presence for any new file, however this patch only checked first two
>> line for SPDX presence. (currently it is nak for other reasons)
>>
>> https://patchwork.kernel.org/patch/10053699/
>>
>> If it makes easy for us, we can use the SPDX as first/second line
>> convention.
>
> I agree we should follow the convention chosen in Linux,
> because we may use the same tools.
> Is it already decided for Linux? Can we influence the decision for Linux?
>
I have posted my comments on other thread. Linux have good reasons to do
it. If we have to use linux tool and common code, we shall adapt to same.
next prev parent reply other threads:[~2017-12-15 10:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 10:28 Olivier Matz
2017-12-08 17:29 ` Ferruh Yigit
2017-12-08 18:04 ` Stephen Hemminger
2017-12-08 18:22 ` Andrew Rybchenko
2017-12-11 5:27 ` Hemant Agrawal
2017-12-11 8:58 ` Olivier MATZ
2017-12-11 17:56 ` Ferruh Yigit
2017-12-12 16:57 ` Olivier MATZ
2017-12-13 5:13 ` Hemant Agrawal
2017-12-14 11:33 ` Hemant Agrawal
2017-12-14 12:58 ` Thomas Monjalon
2017-12-15 10:54 ` Hemant Agrawal [this message]
2017-12-22 15:59 ` [dpdk-dev] [PATCH v2] " Olivier Matz
2017-12-28 11:42 ` Hemant Agrawal
2018-01-05 10:32 ` 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=20232357-08fc-c55e-53e0-a9bf5c3e359b@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
--cc=tdelanerolle@linuxfoundation.org \
--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).