From: Greg KH <greg@kroah.com>
To: Rusty Russell <rusty@au1.ibm.com>
Cc: Mike Anderson <andmike@us.ibm.com>,
linux-kernel@vger.kernel.org, Brian King <brking@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
kai@germaschewski.name, sam@ravnborg.org, akpm@osdl.org
Subject: Re: Question on MODULE_VERSION macro
Date: Mon, 19 Jan 2004 17:17:34 -0800 [thread overview]
Message-ID: <20040120011734.GB6309@kroah.com> (raw)
In-Reply-To: <20040120005915.2A54A17DD8@ozlabs.au.ibm.com>
On Tue, Jan 20, 2004 at 11:57:38AM +1100, Rusty Russell wrote:
> In message <20040119214233.GF967@beaverton.ibm.com> you write:
> > Rusty,
> > Christoph mentioned that a MODULE_VERSION macro may be pending.
>
> Hey, thanks Christoph for the reminder. I stopped when we were
> frozen.
>
> This still seems to apply. Do people think this is huge overkill, or
> a work of obvious beauty and genius?
Looks sane. I'm guessing that modinfo can show this?
> Doesn't put things in sysfs, but Greg was working on that for module
> parameters... Greg?
Oh yeah, I'll dig out that patch later this week. An older version has
been sitting in my bk tree forever, need to update it with the last
changes you sent me.
thanks,
greg k-h
next prev parent reply other threads:[~2004-01-20 1:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040119214233.GF967@beaverton.ibm.com>
2004-01-20 0:57 ` Question on MODULE_VERSION macro Rusty Russell
2004-01-20 1:17 ` Greg KH [this message]
2004-01-20 7:47 ` Rusty Russell
2004-02-20 21:44 ` Brian King
2004-02-21 1:07 ` Rusty Russell
2004-02-22 23:23 ` Sam Ravnborg
2004-02-23 3:51 ` Rusty Russell
2004-02-23 21:17 ` Sam Ravnborg
2004-02-24 6:13 ` Rusty Russell
2004-02-25 21:36 ` Sam Ravnborg
2004-02-26 1:50 ` Rusty Russell
2004-02-26 7:12 ` Sam Ravnborg
2004-03-10 20:49 ` Brian King
2004-03-10 21:08 ` Greg KH
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=20040120011734.GB6309@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=andmike@us.ibm.com \
--cc=brking@us.ibm.com \
--cc=hch@infradead.org \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@au1.ibm.com \
--cc=sam@ravnborg.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