linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Adrian Bunk <bunk@kernel.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ide: use MODULE_VERSION()
Date: Wed, 02 Jan 2008 15:40:20 +0100	[thread overview]
Message-ID: <477BA254.9010702@s5r6.in-berlin.de> (raw)
In-Reply-To: <1199252790.3300.77.camel@perihelion>

Jon Masters wrote:
> On Tue, 2008-01-01 at 22:46 -0600, Matt Domsch wrote:
>> $ modinfo dell_rbu | grep version
>> version:        3.2
>> srcversion:     1D4815D7D6FBEE6612F3C18
> 
> Right. And I was referring to the is above (I forgot it's a CRC32 and
> not a SHA1). But my point is why not codify some "policy" here with
> respect to module versioning, rather than have the latter exist to
> workaround the case that module versions aren't bumped manually.

How about this version scheme:
driver version == Linux kernel version
-- 
Stefan Richter
-=====-==--- ---= ---=-
http://arcgraph.de/sr/

  reply	other threads:[~2008-01-02 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 17:40 [PATCH 1/3] ide: use MODULE_VERSION() Bartlomiej Zolnierkiewicz
2008-01-01 17:53 ` Adrian Bunk
2008-01-01 18:33   ` Bartlomiej Zolnierkiewicz
2008-01-02  2:32     ` Jon Masters
2008-01-02  4:46       ` Matt Domsch
2008-01-02  5:46         ` Jon Masters
2008-01-02 14:40           ` Stefan Richter [this message]
2008-01-02 22:45         ` Bartlomiej Zolnierkiewicz
2008-01-02 22:40           ` Matt Domsch

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=477BA254.9010702@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=Matt_Domsch@dell.com \
    --cc=bunk@kernel.org \
    --cc=bzolnier@gmail.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).