devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Juri Lelli <juri.lelli@arm.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	peterz@infradead.org, Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dietmar.eggemann@arm.com, Russell King <linux@armlinux.org.uk>,
	Mark Brown <broonie@kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Morten Rasmussen <morten.rasmussen@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 6/9] arm, arm64: factorize common cpu capacity default code
Date: Wed, 15 Feb 2017 15:35:41 -0800	[thread overview]
Message-ID: <20170215233541.GA7403@kroah.com> (raw)
In-Reply-To: <CAL_JsqKLiQ2cSffadMWbN2PkqBOiA-6Mx5YVMCehVQNpy7YqrQ@mail.gmail.com>

On Wed, Feb 15, 2017 at 05:17:05PM -0600, Rob Herring wrote:
> On Fri, Feb 10, 2017 at 8:28 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> + *
> >> + * Copyright (C) 2016, ARM Ltd.
> >> + * Written by: Juri Lelli, ARM Ltd.
> >> + *
> >> + * This file is subject to the terms and conditions of the GNU General Public
> >> + * License.  See the file "COPYING" in the main directory of this archive
> >> + * for more details.
> >
> > So, v2 only?  Please be specific.  Even better yet, use a SPDX header if
> > you want to, those are always nice.
> 
> Sorry to hijack this thread, but you're recommending SPDX now? You
> seemed pretty negative on it last time it came up[1]. Or was that just
> in context of the churn of converting existing files?

It was in the context of someone trying to tell someone else to do the
work for them of converting all of the existing files to use SPDX.  I've
never refused a patch from someone adding SPDX identifiers to the
kernel, in fact, _I'm_ the only one that has ever used such an
identifier on a kernel file :)

> Personally, I like the use of SPDX tags over free form license text
> and would like to encourage it for dts files.

Sure, go ahead, I'd encourage it.

thanks,

greg k-h

  reply	other threads:[~2017-02-15 23:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  9:25 [PATCH v2 0/9] Fix issues and factorize arm/arm64 capacity information code Juri Lelli
2017-02-09  9:25 ` [PATCH v2 1/9] Documentation: arm: fix wrong reference number in DT definition Juri Lelli
2017-02-09  9:25 ` [PATCH v2 2/9] Documentation/ABI: add information about cpu_capacity Juri Lelli
2017-02-09  9:25 ` [PATCH v2 3/9] arm: fix return value of parse_cpu_capacity Juri Lelli
2017-02-09  9:25 ` [PATCH v2 4/9] arm: remove wrong CONFIG_PROC_SYSCTL ifdef Juri Lelli
2017-02-09  9:25 ` [PATCH v2 5/9] arm64: " Juri Lelli
     [not found] ` <20170209092525.6654-1-juri.lelli-5wv7dgnIgG8@public.gmane.org>
2017-02-09  9:25   ` [PATCH v2 6/9] arm, arm64: factorize common cpu capacity default code Juri Lelli
2017-02-10 14:28     ` Greg KH
2017-02-13 15:09       ` Juri Lelli
2017-03-09  8:37         ` Juri Lelli
     [not found]       ` <20170210142857.GA18321-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-02-15 23:17         ` Rob Herring
2017-02-15 23:35           ` Greg KH [this message]
2017-02-09  9:25   ` [PATCH v2 7/9] arm,arm64,drivers: reduce scope of cap_parsing_failed Juri Lelli
2017-02-09  9:25 ` [PATCH v2 8/9] arm,arm64,drivers: move externs in a new header file Juri Lelli
2017-02-09  9:25 ` [PATCH v2 9/9] arm, arm64, drivers: add a prefix to drivers arch_topology interfaces Juri Lelli

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=20170215233541.GA7403@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linux@armlinux.org.uk \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=will.deacon@arm.com \
    /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).