From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hemant Agrawal Subject: Re: [PATCH] net: update licence for network headers Date: Fri, 15 Dec 2017 16:24:07 +0530 Message-ID: <20232357-08fc-c55e-53e0-a9bf5c3e359b@nxp.com> References: <20171208102830.2817-1-olivier.matz@6wind.com> <1018d643-eb39-cd23-4094-9ae2a4bcd860@nxp.com> <3574356.e36fbgbura@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Cc: Olivier MATZ , Ferruh Yigit , Andrew Rybchenko , , Stephen Hemminger , Trishan de Lanerolle To: Thomas Monjalon Return-path: Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0078.outbound.protection.outlook.com [104.47.33.78]) by dpdk.org (Postfix) with ESMTP id DE6081B01C for ; Fri, 15 Dec 2017 11:54:13 +0100 (CET) In-Reply-To: <3574356.e36fbgbura@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.