From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: linus.walleij@linaro.org, gnurou@gmail.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/4] gpio: ws16c48: Pass the correct license string to MODULE_LICENSE
Date: Mon, 1 Feb 2016 18:53:29 -0500 [thread overview]
Message-ID: <419b70385461558e4b3d5bdc768d44ff6533f465.1454342013.git.vilhelm.gray@gmail.com> (raw)
In-Reply-To: <35ba3999e8962521bff229f91cbbc1b9554e8c18.1454342013.git.vilhelm.gray@gmail.com>
In-Reply-To: <cover.1454342013.git.vilhelm.gray@gmail.com>
The WinSystems WS16C48 GPIO driver copyright boilerplate lacks the "or
later" verbiage regarding GPL compliant distribution. The MODULE_LICENSE
string should reflect the actual copyright license terms used.
Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
---
drivers/gpio/gpio-ws16c48.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-ws16c48.c b/drivers/gpio/gpio-ws16c48.c
index 9dd9479..d5279a0 100644
--- a/drivers/gpio/gpio-ws16c48.c
+++ b/drivers/gpio/gpio-ws16c48.c
@@ -433,4 +433,4 @@ module_exit(ws16c48_exit);
MODULE_AUTHOR("William Breathitt Gray <vilhelm.gray@gmail.com>");
MODULE_DESCRIPTION("WinSystems WS16C48 GPIO driver");
-MODULE_LICENSE("GPL");
+MODULE_LICENSE("GPL v2");
--
2.4.10
next prev parent reply other threads:[~2016-02-01 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 23:51 [PATCH 0/4] Pass " William Breathitt Gray
2016-02-01 23:51 ` [PATCH 1/4] gpio: 104-dio-48e: " William Breathitt Gray
2016-02-01 23:51 ` [PATCH 2/4] gpio: 104-idi-48: Pass the " William Breathitt Gray
2016-02-01 23:53 ` [PATCH 3/4] gpio: 104-idio-16: " William Breathitt Gray
2016-02-01 23:53 ` William Breathitt Gray [this message]
2016-02-13 22:41 ` [PATCH 0/4] Pass " Linus Walleij
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=419b70385461558e4b3d5bdc768d44ff6533f465.1454342013.git.vilhelm.gray@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®