linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Sangbeom Kim <sbkim73@samsung.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] clk: s2mps11,s3c64xx: Add SPDX license identifiers
Date: Tue, 14 Aug 2018 14:38:21 -0600	[thread overview]
Message-ID: <20180814203821.GA29323@rob-hp-laptop> (raw)
In-Reply-To: <20180807161713.28073-2-krzk@kernel.org>

On Tue,  7 Aug 2018 18:17:12 +0200, Krzysztof Kozlowski wrote:
> Replace GPL v2.0 and v2.0+ license statements with SPDX license
> identifiers.
> 
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
>  drivers/clk/clk-s2mps11.c                         | 21 +++++----------------
>  include/dt-bindings/clock/samsung,s2mps11.h       |  5 +----
>  include/dt-bindings/clock/samsung,s3c64xx-clock.h |  7 ++-----
>  3 files changed, 8 insertions(+), 25 deletions(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2018-08-14 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 16:17 [PATCH 1/3] clk: max77686: Add SPDX license identifiers Krzysztof Kozlowski
2018-08-07 16:17 ` [PATCH 2/3] clk: s2mps11,s3c64xx: " Krzysztof Kozlowski
2018-08-14 20:38   ` Rob Herring [this message]
2018-08-27 21:17   ` Stephen Boyd
2018-08-07 16:17 ` [PATCH 3/3] clk: s2mps11: Use existing defines from bindings for clock IDs Krzysztof Kozlowski
2018-08-14 20:37   ` Rob Herring
2018-08-27 21:18   ` Stephen Boyd
2018-08-27 21:17 ` [PATCH 1/3] clk: max77686: Add SPDX license identifiers Stephen Boyd

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=20180814203821.GA29323@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=javier@dowhile0.org \
    --cc=krzk@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=sbkim73@samsung.com \
    --cc=sboyd@kernel.org \
    /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).