From: Matt Domsch <Matt_Domsch@dell.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-scsi@vger.kernel.org
Subject: Re: MODULE_VERSION for scsi drivers
Date: Tue, 27 Apr 2004 09:59:05 -0500 [thread overview]
Message-ID: <20040427145905.GB20421@lists.us.dell.com> (raw)
In-Reply-To: <20040427153145.A17739@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On Tue, Apr 27, 2004 at 03:31:45PM +0100, Christoph Hellwig wrote:
> On Tue, Apr 27, 2004 at 08:10:50AM -0500, Matt Domsch wrote:
> > Per include/linux/module.h:
> > Using this automatically adds a checksum of the .c files and the
> > local headers to the end. Use MODULE_VERSION("") if you want just
> > this. Macro includes room for this.
> >
> > So for modules which don't appear to have their own versioning, we use
> > the "" mechanism to simply generate the checksum for the file. This
> > still allows tools (ala DKMS eventually) to note if something in the
> > module changed even if the version string didn't.
>
> That's totally braindead. If you want to use a scheme like that talk
> rusty into generating this without needing to add anything to the driver.
Yeah, that thought crossed my mind at 4am too. I just pinged Rusty,
and will see about doing such myself regardless.
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 --]
prev parent reply other threads:[~2004-04-27 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 4:09 MODULE_VERSION for scsi drivers Matt Domsch
2004-04-27 4:15 ` Randy.Dunlap
2004-04-27 8:22 ` Jan-Benedict Glaw
2004-04-27 13:10 ` Matt Domsch
2004-04-27 14:31 ` Christoph Hellwig
2004-04-27 14:59 ` Matt Domsch [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=20040427145905.GB20421@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@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