From: "Arend van Spriel" <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: "rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Tso Ted" <tytso@mit.edu>, "Keith Packard" <keithp@keithp.com>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Ralf Baechle" <ralf@linux-mips.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"David Woodhouse" <dwmw2@infradead.org>,
"Stephen Hemminger" <shemminger@vyatta.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] module: Clarify usage of MODULE_LICENSE()
Date: Mon, 9 Apr 2012 10:04:40 +0200 [thread overview]
Message-ID: <4F829818.6040600@broadcom.com> (raw)
In-Reply-To: <1333903588-32608-1-git-send-email-mcgrof@frijolero.org>
On 04/08/2012 06:46 PM, Luis R. Rodriguez wrote:
> include/linux/module.h | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/module.h b/include/linux/module.h
> index fbcafe2..8d36d86 100644
> --- a/include/linux/module.h
> +++ b/include/linux/module.h
> - * This exists for several reasons
> + * The MODULE_LICENSE() exists for several reasons:
> + * 0. So EXPORT_SYMBOL_GPL() allows the module to use its symbols
It seems there is some tab/space mixup here. Also not sure if the above
statement is clear or correct. Correct me if I am wrong, but I thought
it put a requirement on other modules to be able to use its symbols.
> * 1. So modinfo can show license info for users wanting to vet their setup
> * is free
> * 2. So the community can ignore bug reports including proprietary modules
Gr. AvS
next prev parent reply other threads:[~2012-04-09 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 16:46 [PATCH v2] module: Clarify usage of MODULE_LICENSE() Luis R. Rodriguez
2012-04-09 8:04 ` Arend van Spriel [this message]
2012-04-09 12:36 ` Luis R. Rodriguez
2012-05-07 3:00 ` Rusty Russell
2012-05-07 22:48 ` Luis R. Rodriguez
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=4F829818.6040600@broadcom.com \
--to=arend@broadcom.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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