From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 3c509 Power Management (take 2)
Date: Fri, 01 Mar 2002 19:58:26 -0500 [thread overview]
Message-ID: <3C8023B2.FB6ADCB9@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0203010826180.26745-100000@netfinity.realnet.co.sz> <Pine.LNX.4.44.0203011222010.31530-100000@netfinity.realnet.co.sz> <20020301093317.I22608@lynx.adilger.int>
Andreas Dilger wrote:
>
> On Mar 01, 2002 12:24 +0200, Zwane Mwaikambo wrote:
> > -static char versionA[] __initdata = DRV_NAME ".c:" DRV_VERSION " " DRV_RELDATE "becker@scyld.com\n";
> > +static char versionA[] __initdata = DRV_NAME ".c:" DRV_VERSION " " DRV_RELDATE " becker@scyld.com\n";
> > static char versionB[] __initdata = "http://www.scyld.com/network/3c509.html\n";
>
> Should this still be reporting becker@scyld.com if you guys are now
> maintaining it? This is doubly true of the URL, since that URL will
> not have the driver that is in the kernel.
I leave it in there mainly for two reasons,
first, for several drivers, it lets people know the base version upon
which the driver was based. This is useful if someone wanted to do some
merging of a more recent Becker version, and
second, as a courtesy, since typically the code in the driver is still
well over 60% Becker's even after all the Linus-tree modifications.
Jeff
--
Jeff Garzik |
Building 1024 |
MandrakeSoft | Choose life.
next prev parent reply other threads:[~2002-03-02 0:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 6:30 [PATCH] 3c509 Power Management Zwane Mwaikambo
2002-03-01 10:24 ` [PATCH] 3c509 Power Management (take 2) Zwane Mwaikambo
2002-03-01 16:33 ` Andreas Dilger
2002-03-02 0:58 ` Jeff Garzik [this message]
2002-03-02 20:48 ` christophe barbé
2002-03-02 21:16 ` Jeff Garzik
2002-03-02 21:19 ` christophe barbé
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=3C8023B2.FB6ADCB9@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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