From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jes Sorensen <jes@sgi.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] mspec
Date: Tue, 20 Jun 2006 09:11:16 -0700 [thread overview]
Message-ID: <20060620091116.e81d4360.rdunlap@xenotime.net> (raw)
In-Reply-To: <yq0hd2gyvl7.fsf@jaguar.mkp.net>
On 20 Jun 2006 06:23:16 -0400 Jes Sorensen wrote:
> >>>>> "Randy" == Randy Dunlap <rdunlap@xenotime.net> writes:
>
> Randy> On 19 Jun 2006 05:20:23 -0400 Jes Sorensen wrote:
> >> +MODULE_AUTHOR("Silicon Graphics, Inc.");
> >> +MODULE_DESCRIPTION("Driver for SGI SN special memory operations");
> >> +MODULE_LICENSE("GPL"); +MODULE_INFO(supported, "external");
>
> Randy> What does that last line mean? what does "external" mean?
> Randy> There are no other source files in the 2.6.17 tree that say
> Randy> anything like that.
>
> Randy> And of the 1800+ MODULE_AUTHOR() lines, SGI seems to be
> Randy> dominant is using company instead of a person for AUTHOR. Yes,
> Randy> there are a few others as well. module.h says: /* Author,
> Randy> ideally of form NAME <EMAIL>[, NAME <EMAIL>]*[ and NAME
> Randy> <EMAIL>] */
>
> Randy,
>
> I went back and looked through the usages of these macros and it does
> indeed seem that nobody else tries to state 'supported' in MODULE_INFO
> so I have removed that and added an email address to the author line,
> which should always stay valid.
Hi Jes,
Thanks for doing that, esp. the 'supported' part.
> +MODULE_AUTHOR("Silicon Graphics, Inc. <linux-altix@sgi.com>");
> +MODULE_DESCRIPTION("Driver for SGI SN special memory operations");
> +MODULE_LICENSE("GPL");
---
~Randy
next prev parent reply other threads:[~2006-06-20 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 9:20 Jes Sorensen
2006-06-19 15:58 ` Randy.Dunlap
2006-06-20 8:06 ` Jes Sorensen
2006-06-20 11:08 ` Robin Holt
2006-06-20 10:23 ` Jes Sorensen
2006-06-20 16:11 ` Randy.Dunlap [this message]
2006-06-27 12:50 ` Jes Sorensen
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=20060620091116.e81d4360.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®