All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Watchdog Drivers <linux-watchdog@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/2] SPDX conversion for watchdog drivers
Date: Wed, 17 May 2023 14:21:38 +0700	[thread overview]
Message-ID: <20230517072140.1086660-1-bagasdotme@gmail.com> (raw)

This mini SPDX conversion series focuses on watchdog drivers. It is
splitted from v2 of my SPDX conversion series that is triggered by
Didi's GPL full name fixes [1] to easify review.

The only missing bit compared to v2 is driver for SiByte SB1 watchdog
driver (drivers/watchdog/sb_wdog.c). The driver is skipped because
although theoretically SPDX license identifier for it is
GPL-1.0-only OR GPL-2.0-only, it doesn't satisfy spdxcheck test.
On the other hand, GPL-1.0+ isn't the answer either, since it will
include GPL v3. With above constraints, the licensing requirement
for sb_wdog can't be expressed acceptably, and so it is omitted
from this series.

Happy reviewing!

[1]: https://lore.kernel.org/linux-spdx/20230512100620.36807-1-bagasdotme@gmail.com/

Bagas Sanjaya (2):
  watchdog: Convert GPL 2.0 notice to SPDX identifier
  watchdog: ibmasr: Replace GPL license notice with SPDX identifier

 drivers/watchdog/ep93xx_wdt.c     | 5 +----
 drivers/watchdog/ibmasr.c         | 3 +--
 drivers/watchdog/m54xx_wdt.c      | 4 +---
 drivers/watchdog/max63xx_wdt.c    | 5 +----
 drivers/watchdog/moxart_wdt.c     | 4 +---
 drivers/watchdog/octeon-wdt-nmi.S | 5 +----
 drivers/watchdog/orion_wdt.c      | 4 +---
 drivers/watchdog/rtd119x_wdt.c    | 2 +-
 drivers/watchdog/sbc_fitpc2_wdt.c | 4 +---
 drivers/watchdog/ts4800_wdt.c     | 4 +---
 drivers/watchdog/ts72xx_wdt.c     | 4 +---
 11 files changed, 11 insertions(+), 33 deletions(-)


base-commit: 10f67d1fd275528e62109de2ece26371833638e5
-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2023-05-17  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  7:21 Bagas Sanjaya [this message]
2023-05-17  7:21 ` [PATCH 1/2] watchdog: Convert GPL 2.0 notice to SPDX identifier Bagas Sanjaya
2023-05-17  8:37   ` Mika Westerberg
2023-05-17 12:15   ` Guenter Roeck
2023-05-17  7:21 ` [PATCH 2/2] watchdog: ibmasr: Replace GPL license notice with " Bagas Sanjaya
2023-05-17 12:16   ` Guenter Roeck

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=20230517072140.1086660-1-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wim@linux-watchdog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.