linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-spdx@vger.kernel.org,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: [patch 04/10] clocksource/drivers/armada-370-xp: Convert to SPDX identifier
Date: Tue, 10 May 2022 19:24:41 +0200 (CEST)	[thread overview]
Message-ID: <20220510171254.592781786@linutronix.de> (raw)
In-Reply-To: 20220510171003.952873904@linutronix.de

The license information clearly states GPL version 2 only. The extra text
which excludes warranties is an excerpt of the corresponding GPLv2 clause
11.

So the SPDX identifier covers it completely.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Gregory Clement <gregory.clement@free-electrons.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
---
 drivers/clocksource/timer-armada-370-xp.c |    5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

--- a/drivers/clocksource/timer-armada-370-xp.c
+++ b/drivers/clocksource/timer-armada-370-xp.c
@@ -1,3 +1,4 @@
+// SPDX-License-Identifier: GPL-2.0
 /*
  * Marvell Armada 370/XP SoC timer handling.
  *
@@ -7,10 +8,6 @@
  * Gregory CLEMENT <gregory.clement@free-electrons.com>
  * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
  *
- * This file is licensed under the terms of the GNU General Public
- * License version 2.  This program is licensed "as is" without any
- * warranty of any kind, whether express or implied.
- *
  * Timer 0 is used as free-running clocksource, while timer 1 is
  * used as clock_event_device.
  *


  parent reply	other threads:[~2022-05-10 17:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 17:24 [patch 00/10] clocksource/drivers: Convert to SPDX identifiers Thomas Gleixner
2022-05-10 17:24 ` [patch 01/10] clocksource/drivers/bcm_kona: Convert to SPDX identifier Thomas Gleixner
2022-05-10 18:26   ` Florian Fainelli
2022-05-16  9:30   ` Daniel Lezcano
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 02/10] clocksource/drivers/jcore: " Thomas Gleixner
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 03/10] clocksource/drivers/mips-gic-timer: " Thomas Gleixner
2022-05-12  0:17   ` Serge Semin
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` Thomas Gleixner [this message]
2022-05-13 12:30   ` [patch 04/10] clocksource/drivers/armada-370-xp: " Gregory CLEMENT
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 05/10] clocksource/drivers/digicolor: " Thomas Gleixner
2022-05-11  3:28   ` Baruch Siach
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 06/10] clocksource/drivers/lpc32xx: " Thomas Gleixner
2022-05-10 18:33   ` Vladimir Zapolskiy
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 07/10] clocksource/drivers/orion: " Thomas Gleixner
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 08/10] clocksource/drivers/pistachio: " Thomas Gleixner
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 09/10] clocksource/drivers/timer-sun4i: " Thomas Gleixner
2022-05-22  7:36   ` Jernej Škrabec
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner
2022-05-10 17:24 ` [patch 10/10] clocksource/drivers/timer-sun5i: " Thomas Gleixner
2022-05-22  7:37   ` Jernej Škrabec
2022-05-27  8:35   ` [tip: timers/core] " tip-bot2 for Thomas Gleixner

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=20220510171254.592781786@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.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).