From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 0FF881D90 for ; Thu, 14 Dec 2017 13:58:53 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8021F2076C; Thu, 14 Dec 2017 07:58:52 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 14 Dec 2017 07:58:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=d5cVjFsONoUuj7o/dbGnmKDtnp p++DyltuRqwYk1pkE=; b=c+d+oRNpnFITD5vK5DYyGfuGg91BDHeG60jlnZi5Pf n3khn99Li3HIM/5SuP3HN/lyZVsX7Z0Kohd7Owehn9QDMIAP6o8FSxMW3qWWuvrI EXHoVkAkKL0IUuIg0j05mGGVbLAJ5YyFJlykg8Nf9QMgjdCU8PwoOoPV6l0Xo0bc s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=d5cVjF sONoUuj7o/dbGnmKDtnpp++DyltuRqwYk1pkE=; b=qRKm5fkwsb9MblR8jqXxTn fQIoguhXtBSvk5FVcjuJ8aJ5iz9Tsqmq7ujs0ik9oj27OnypJNr4ReDwinbX/5TC //TiswnAwZbZjh4ORp1te8UVFtcJFGlX6UKm8CVJ+5+DkzEbwc8E2TYbrVUm5kiZ U5d3EfrJH92ns1B2gVKpy0b80vFkHOWgp3bKwzSrnqv9zOJobdmbUJSI9NxlLA0c poJVqzb7xmpSdaQqYjzaZomHm/gqx8f2F7jtg0e/N1KhbITaIT6Gh2z1R5Vw4dhl pICtxX9aCyFYDkqjWziJxaH5fnSA6PCIC/ZyJ/YcDChedZG7yC1Yudf+Du48cTmg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 2B8A9241E2; Thu, 14 Dec 2017 07:58:52 -0500 (EST) From: Thomas Monjalon To: Hemant Agrawal Cc: Olivier MATZ , Ferruh Yigit , Andrew Rybchenko , dev@dpdk.org, Stephen Hemminger , Trishan de Lanerolle Date: Thu, 14 Dec 2017 13:58:51 +0100 Message-ID: <3574356.e36fbgbura@xps> In-Reply-To: References: <20171208102830.2817-1-olivier.matz@6wind.com> <1018d643-eb39-cd23-4094-9ae2a4bcd860@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] net: update licence for network headers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 12:58:53 -0000 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?