mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
	linux-s390@vger.kernel.org, linux-pci@vger.kernel.org,
	Sebastian Ott <sebott@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Gerald Schaefer <gerald.schaefer@de.ibm.com>
Subject: [PATCH] PCI: Add SPDX tag for s390_pci_hpc.c
Date: Mon, 29 Jan 2018 18:40:42 -0600	[thread overview]
Message-ID: <20180130003559.15416.18047.stgit@bhelgaas-glaptop.roam.corp.google.com> (raw)

I previously posted patches [1] to add SPDX tags to all drivers/pci files
except drivers/pci/hotplug/s390_pci_hpc.c.  I omitted that one because it
contained only a "License: GPL" comment, which I thought was ambiguous.

However, I think it is actually unambiguous because the file was added with
a 'MODULE_LICENSE("GPL")', and include/linux/module.h shows that means "GPL
v2 or later".

So this patch adds the GPL-2.0+ tag to the file.  I plan to include this
for v4.16 unless somebody objects.

[1] https://lkml.kernel.org/r/20180126212536.31503.43805.stgit@bhelgaas-glaptop.roam.corp.google.com

---

Bjorn Helgaas (1):
      PCI: Add SPDX GPL-2.0+ to replace implicit GPL v2 or later statement


 drivers/pci/hotplug/s390_pci_hpc.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

             reply	other threads:[~2018-01-30  0:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  0:40 Bjorn Helgaas [this message]
2018-01-30  0:40 ` [PATCH] PCI: Add SPDX GPL-2.0+ to replace implicit GPL v2 or later statement Bjorn Helgaas
2018-01-30  7:13   ` Greg Kroah-Hartman
2018-01-30 12:44   ` Sebastian Ott
2018-02-08 14:20   ` Philippe Ombredanne
2018-02-08 14:17 ` [PATCH] PCI: Add SPDX tag for s390_pci_hpc.c Philippe Ombredanne

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=20180130003559.15416.18047.stgit@bhelgaas-glaptop.roam.corp.google.com \
    --to=helgaas@kernel.org \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=sebott@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®