From: Matt Domsch <Matt_Domsch@dell.com>
To: Rusty Russell <rusty@rustcorp.com.au>, greg@kroah.com
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: always store MODULE_VERSION("") data?
Date: Thu, 29 Apr 2004 21:55:58 -0500 [thread overview]
Message-ID: <20040430025558.GA26551@lists.us.dell.com> (raw)
In-Reply-To: <1083200122.9669.16.camel@bach>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On Thu, Apr 29, 2004 at 10:55:22AM +1000, Rusty Russell wrote:
> On Wed, 2004-04-28 at 00:58, Matt Domsch wrote:
> > How hard would it be to always include the space for the
> > MODULE_VERSION("") data rather than specifying it in each file that
> > doesn't care, and only modules with their own versioning could put
> > MODULE_VERSION("myversion") to override the default?
>
> If this is desirable, I would prefer to separate "version" and
> "srcversion" (or some other name). This is done in the following patch
> (we still mangle RCS-style version strings), for all modules using
> MODULE_VERSION, and adds CONFIG_MODULE_SRCVERSION_ALL if you want it in
> all modules.
>
> Works here, but these changes tend to break things...
Works for me too. All modules regardless if if they have a
MODULE_VERSION() entry get the srcversion field in .modinfo. If they
also have a MODULE_VERSION(), that data shows up in .modinfo also.
This is exactly what I wanted.
Now to find GregKH's patch to export this stuff via sysfs...
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-30 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 14:58 always store MODULE_VERSION("") data? Matt Domsch
2004-04-29 0:55 ` Rusty Russell
2004-04-30 2:55 ` Matt Domsch [this message]
2004-05-01 5:43 ` Greg KH
2004-09-04 13:37 ` Matt Domsch
2004-05-02 18:31 ` Sam Ravnborg
2004-05-03 2:20 ` Rusty Russell
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=20040430025558.GA26551@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.