From: Matt Domsch <Matt_Domsch@dell.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>,
jamagallon@able.es, linux-kernel@vger.kernel.org
Subject: Re: 3c59x went nuts between .15-mm3 and .15-mm4
Date: Thu, 19 Jan 2006 17:46:12 -0600 [thread overview]
Message-ID: <20060119234612.GA16789@lists.us.dell.com> (raw)
In-Reply-To: <20060119152757.6d7f3924.akpm@osdl.org>
On Thu, Jan 19, 2006 at 03:27:57PM -0800, Andrew Morton wrote:
> Steffen Klassert <klassert@mathematik.tu-chemnitz.de> wrote:
> >
> > The driver version did not increase since more than three years.
> > But perhaps it is a good idea to maintain the driver version.
>
> Just nuke it. Per-driver versioning is pretty meaningless and we should
> and do identify driver versions by the version of the top-level kernel
> which contains them.
With all due respect, per-driver versioning in mainline may be
meaningless (and as you note, modinfo already carries the kernel
version in it), but as soon as it hits a vendor kernel, it means very
much, and is the primary method of denoting to a larger (and mostly
non-driver-developer) audience what hardware is supported, and what
critical (to the vendor) bugs have been addressed.
And some tools, such as DKMS, make explicit use of the MODULE_VERSION
tag to automate updating individual drivers without necessarily changing out the
whole vendor kernel. Once the vendor kernel "catches up" with the
equivalent driver, DKMS won't replace it any more. All of the drivers
critical to Dell are separately versioned exactly for this reason, and
those tags are in the code submitted to mainline. (3c59x isn't in
that category I admit).
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
prev parent reply other threads:[~2006-01-19 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 21:53 J.A. Magallon
2006-01-19 22:31 ` Steffen Klassert
2006-01-19 23:27 ` Andrew Morton
2006-01-19 23:45 ` Steffen Klassert
2006-01-19 23:46 ` 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=20060119234612.GA16789@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=akpm@osdl.org \
--cc=jamagallon@able.es \
--cc=klassert@mathematik.tu-chemnitz.de \
--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
Powered by JetHome