From: Chris Rankin <rankinc@pacbell.net>
To: axboe@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] MODULE_LICENSE for loop device
Date: Wed, 24 Oct 2001 12:25:36 -0700 (PDT) [thread overview]
Message-ID: <200110241925.f9OJPaOw001568@twopit.underworld> (raw)
Hi,
Here's a totally trivial patch (against 2.4.13) to give the loop
device a MODULE_LICENSE tag.
Cheers,
Chris
--- drivers/block/loop.c.orig Wed Oct 24 01:03:59 2001
+++ drivers/block/loop.c Wed Oct 24 12:23:34 2001
@@ -951,6 +951,7 @@
*/
MODULE_PARM(max_loop, "i");
MODULE_PARM_DESC(max_loop, "Maximum number of loop devices (1-255)");
+MODULE_LICENSE("GPL");
int loop_register_transfer(struct loop_func_table *funcs)
{
reply other threads:[~2001-10-24 19:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200110241925.f9OJPaOw001568@twopit.underworld \
--to=rankinc@pacbell.net \
--cc=axboe@suse.de \
--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®