From: Jason Lunz <lunz@falooley.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Olaf Hering <olh@suse.de>, netdev@vger.kernel.org
Subject: Re: incorrect usage of UTS_RELEASE in bcm43xx_get_drvinfo
Date: Fri, 21 Jul 2006 15:13:30 -0400 [thread overview]
Message-ID: <20060721191329.GA15478@knob.reflex> (raw)
In-Reply-To: <200607212103.23954.mb@bu3sch.de>
On Fri, Jul 21, 2006 at 09:03:23PM +0200, Michael Buesch wrote:
> I am not going to maintain a bogus version number.
> What about simply returning 1.0 and be done with it.
> I don't think it matters. 1.0 is as bogus as any other value.
Put it to use! Increment it whenever there's a major change in the
driver, like the locking rewrite or the init routine rewrite. At the
very least, it makes it easier to rule certain things out if a user
reports lockup or something.
Jason
next prev parent reply other threads:[~2006-07-21 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 18:59 incorrect usage of UTS_RELEASE in bcm43xx_get_drvinfo Olaf Hering
2006-07-21 19:03 ` Michael Buesch
2006-07-21 19:12 ` Olaf Hering
2006-07-21 19:13 ` Jason Lunz [this message]
2006-07-21 19:27 ` Michael Buesch
2006-07-21 20:05 ` Jason Lunz
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=20060721191329.GA15478@knob.reflex \
--to=lunz@falooley.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=olh@suse.de \
/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).