Received: by 10.223.176.46 with SMTP id f43csp4543874wra; Tue, 23 Jan 2018 10:45:13 -0800 (PST) X-Google-Smtp-Source: AH8x225RxAkVn4zjB3AzHhQgpSVmuJUg2QbVR/1sgZb/Cxe6otSwgQdcK3xZuc+vKO89Lav9oPCw X-Received: by 10.36.116.20 with SMTP id o20mr5135702itc.135.1516733113126; Tue, 23 Jan 2018 10:45:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516733113; cv=none; d=google.com; s=arc-20160816; b=xA1fBeITyHUX/+MkQ00D4pcoaPDEWV0Gjo343wnvr8VM1YwPxNm7RUYlRh4iA2AcVd inVKMadikGOw+lTOspWKaDld2tbZAn96K/zvB71Pkz/5KMnd6tahLx+QbWAil3Vyskvv LTh27+9oU/oFWnmgzmpsIL3m/bqxaiyxK9WibDVX4u0NQsYc660mEPAcDOvxKkQ2xE1j wBSgS6E/azxw+doRlGIzeuwaxGyW3xNb6OUa4YDb+AEJhoD+CLcq6hixKPnll7pd3+1g YLjkPqZG4kWAImdgKR33P8SXDg7TUsXI8TQLxtLTFDwg/xMRFmkAsLgTR4TbdPpgNeNw pfwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=dkUWlZciHqCk2IGG8byXpcASh8RQshC053Lcz6YirOY=; b=O6Y8qUBNyp+dZJzhnqgdLOIICjne/5FMF015rOf2gvmGDNL83JqfO3BXbhquOUc4aw NX8UH7+eNpg/MQHWwOLhGDW6Qvtetl6ZCYqRoJ2dDcwMFgxZk1lvJJ/zFOq7qG0tFIrm s4b6rS8gN3rEAdnFujxrNmvM9EpnYk6CRF+ZuyqxAOL8fEzmnRRqt8SMJfuHFHazRYzs mjFijjspGYJXQslHgkGJ3YKbCaAKIlj914+sKluyCU+YyHgXmPCyOPg9auBi6L9OhY+d SDgSNyG+thcbxJ8vb8JX7DMt2RcHe/g1u22gZnoQENpU1qkr7Ew/VvwV4gMP461l1BrU 5PuQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x63si585807ite.133.2018.01.23.10.44.59; Tue, 23 Jan 2018 10:45:13 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752291AbeAWSof (ORCPT + 99 others); Tue, 23 Jan 2018 13:44:35 -0500 Received: from mailgw01.mediatek.com ([210.61.82.183]:3902 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752004AbeAWSoe (ORCPT ); Tue, 23 Jan 2018 13:44:34 -0500 X-UUID: a8a8e678d43f4017b18f988ca0187185-20180124 Received: from mtkexhb02.mediatek.inc [(172.21.101.103)] by mailgw01.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1960121481; Wed, 24 Jan 2018 02:44:28 +0800 Received: from mtkcas08.mediatek.inc (172.21.101.126) by mtkmbs01n1.mediatek.inc (172.21.101.68) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 24 Jan 2018 02:44:27 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas08.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1210.3 via Frontend Transport; Wed, 24 Jan 2018 02:44:27 +0800 Message-ID: <1516733067.15199.41.camel@mtkswgap22> Subject: Re: [PATCH 05/12] arm64: dts: mt7622: add PMIC MT6380 related nodes From: Sean Wang To: Philippe Ombredanne CC: Rob Herring , Matthias Brugger , Mark Rutland , , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , LKML , Mark Brown , "Greg Kroah-Hartman" Date: Wed, 24 Jan 2018 02:44:27 +0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Philippe Really appreciate your info and detailed explanation. it's clear how correct way to add GPDX license identifier. I will have a follow-up. Sean On Tue, 2018-01-23 at 11:46 +0100, Philippe Ombredanne wrote: > Sean, > sorry for the late reply and thanks you for this research. > > On Fri, Jan 12, 2018 at 4:33 AM, Sean Wang wrote: > > Currently, I'm really confused about what usage STYLE of SPDX license > > identifier I should use for each type of file. > > > > could you point me where I can find the related document describing SPDX > > usage style for those files expected by the community in the future? > > The doc is in this patchset [1] > > [1] https://lkml.org/lkml/2017/12/28/326 > > > > I found more than one way STYLE of SPDX present at current code, for > > example as below. If there's no absolute definition for them, and then > > which way that is better? > > 1) > > for *.dts, applied with "// " at head or within " /* */ " not at head > > such as > > > > arch/arm/boot/dts/bcm953012hr.dts:2: * SPDX-License-Identifier: > > BSD-3-Clause > > This is a "style bug". The comment style for .dts should be // > > > 2) > > for *.c, applied with "// " at head or within " /* */ " not at head > > such as > > drivers/soc/xilinx/zynqmp/pm.c:10: * SPDX-License-Identifier: GPL-2.0+ > > This is a "style bug". The comment style for .c should be // > > > 3) > > for *.h, applied with "// " at head or within " /* */ " at head > > such as > > drivers/usb/dwc3/gadget.h:1:// SPDX-License-Identifier: GPL-2.0 > > This is a "style bug". The comment style for .h should be /**/ > > > 4) > > no issue, Makefile, or Kconfig, definitely applied with "# " at head > > That's the correct way. > > So the net-net is that these "style bugs" should be fixed. >