From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] dma: bcm2835: make license text and module license match
Date: Tue, 23 Oct 2018 13:06:07 +0200 [thread overview]
Message-ID: <1540292769-5905-3-git-send-email-stefan.wahren@i2se.com> (raw)
In-Reply-To: <1540292769-5905-1-git-send-email-stefan.wahren@i2se.com>
The license text is specifying GPL v2 or later but the MODULE_LICENSE
is set to GPL v2 which means GNU Public License v2 only. So choose the
license text as the correct one.
Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
---
drivers/dma/bcm2835-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/bcm2835-dma.c b/drivers/dma/bcm2835-dma.c
index 847f84a..112b071 100644
--- a/drivers/dma/bcm2835-dma.c
+++ b/drivers/dma/bcm2835-dma.c
@@ -1064,4 +1064,4 @@ module_platform_driver(bcm2835_dma_driver);
MODULE_ALIAS("platform:bcm2835-dma");
MODULE_DESCRIPTION("BCM2835 DMA engine driver");
MODULE_AUTHOR("Florian Meier <florian.meier@koalo.de>");
-MODULE_LICENSE("GPL v2");
+MODULE_LICENSE("GPL");
--
2.7.4
next prev parent reply other threads:[~2018-10-23 11:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 11:06 [PATCH 0/3] Fix MODULE_LICENSE of bcm2835 drivers Stefan Wahren
2018-10-23 11:06 ` [PATCH 1/3] clk: bcm2835: make license text and module license match Stefan Wahren
2018-10-23 18:31 ` Eric Anholt
2018-11-06 17:35 ` Stephen Boyd
2018-10-23 11:06 ` Stefan Wahren [this message]
2018-11-11 9:09 ` [PATCH 2/3] dma: " Vinod Koul
2018-10-23 11:06 ` [PATCH 3/3] spi: " Stefan Wahren
2018-11-14 22:27 ` Applied "spi: bcm2835: make license text and module license match" to the spi tree Mark Brown
2018-11-07 18:50 ` [PATCH 0/3] Fix MODULE_LICENSE of bcm2835 drivers Stefan Wahren
2018-11-09 18:48 ` Florian Kauer
2018-11-10 11:37 ` Stefan Wahren
2018-11-10 11:45 ` kernel at martin.sperl.org
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=1540292769-5905-3-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=linux-arm-kernel@lists.infradead.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).