From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <laughing@shared-source.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac5
Date: Fri, 31 Aug 2001 11:11:33 +1000 [thread overview]
Message-ID: <8483.999220293@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Fri, 31 Aug 2001 01:33:11 +0100." <20010831013311.A8535@lightning.swansea.linux.org.uk>
On Fri, 31 Aug 2001 01:33:11 +0100,
Alan Cox <laughing@shared-source.org> wrote:
>2.4.9-ac5
>o Add MODULE_LICENSE tagging (me)
__module_license needs to be static. Otherwise we get problems when
MODULE_LICENSE() is used in two objects which are linked into the same
module. Given the legal requirements for copyright etc., I expect
people to put MODULE_LICENSE in every source file, not just one.
What do you need for licence support in modutils? Obviously modinfo
needs to print it, but what about insmod? Should insmod issue warning
messages for proprietary modules? What about ksymoops? IOW, what was
the reason for adding MODULE_LICENSE?
next prev parent reply other threads:[~2001-08-31 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 0:33 Linux 2.4.9-ac5 Alan Cox
2001-08-31 1:11 ` Keith Owens [this message]
2001-08-31 1:26 ` Alan Cox
2001-08-31 1:48 ` Keith Owens
2001-08-31 5:43 ` Albert D. Cahalan
2001-08-31 14:05 ` Alan Cox
2001-08-31 17:07 ` Jamie Lokier
2001-08-31 13:52 ` Alan Cox
2001-08-31 3:58 ` Robert Love
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=8483.999220293@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=laughing@shared-source.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