public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Jim Cromie <jcromie@divsol.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: newbie PATCH: add MODULE_AUTHORS_VERSION macro
Date: Wed, 06 Mar 2002 15:04:38 +1100	[thread overview]
Message-ID: <13833.1015387478@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 05 Mar 2002 17:17:49 PDT." <3C85602D.2090809@divsol.com>

On Tue, 05 Mar 2002 17:17:49 -0700, 
Jim Cromie <jcromie@divsol.com> wrote:
>[jimc@groucho linux]$ diff -u module.h module.h.new
>--- module.h    Wed Feb 27 04:22:33 2002
>+++ module.h.new    Tue Mar  5 15:39:39 2002
>@@ -206,6 +206,10 @@
> const char __module_author[] __attribute__((section(".modinfo"))) =     
>   \
> "author=" name
> 
>+#define MODULE_AUTHORS_VERSION(name)                       \
>+const char __module_authors_version[] 
>__attribute__((section(".modinfo"))) = \
>+"authors_version=" name
>+
> #define MODULE_DESCRIPTION(desc)                       \
> const char __module_description[] __attribute__((section(".modinfo"))) 
>=   \
> "description=" desc
>
>1. grep sources and patch modules which have a VERSION of some sort, like
>
>arch/i386/kernel/mtrr.c:#define MTRR_VERSION            "1.40 (20010327)"

mtrr cannot be a module, bool CONFIG_MTRR.

>arch/i386/kernel/microcode.c:#define MICROCODE_VERSION     "1.09"

MODULE_DESCRIPTION("Intel CPU (IA-32) microcode update driver" MICROCODE_VERSION);

No need for another module_* macro.


      reply	other threads:[~2002-03-06  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  0:17 newbie PATCH: add MODULE_AUTHORS_VERSION macro Jim Cromie
2002-03-06  4:04 ` Keith Owens [this message]

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=13833.1015387478@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=jcromie@divsol.com \
    --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