From: Adrian Bunk <bunk@kernel.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/net/: remove CVS keywords
Date: Tue, 3 Jun 2008 21:14:08 +0300 [thread overview]
Message-ID: <20080603181408.GC2663@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <48354660.7060500@pobox.com>
On Thu, May 22, 2008 at 06:09:36AM -0400, Jeff Garzik wrote:
> Adrian Bunk wrote:
>> This patch removes some CVS keywords that weren't updated for a long
>> time.
>>
>> I haven't touched drivers that looked as if they might still be used.
>>
>> In three drivers I've also removed printk's printing them since they
>> were part of several printk's in a row and it doesn't make sense to
>> print ancient version information to the user.
>>
>> Signed-off-by: Adrian Bunk <bunk@kernel.org>
>
> I'm fine with removing CVS keywords, but I do not agree with removing
> net driver version numbers that have been in the drivers for a while.
Below is the part of the patches that removes these printk's.
Do CVS $Revision tags that haven't been updated for ages really qualify
as net driver version numbers?
I can resend the patch with these changes removed, I'm just asking
whether you might confuse this with regular version numbers.
> Jeff
cu
Adrian
--- a/drivers/net/82596.c
+++ b/drivers/net/82596.c
@@ -59,9 +59,6 @@
#include <asm/pgtable.h>
#include <asm/cacheflush.h>
-static char version[] __initdata =
- "82596.c $Revision: 1.5 $\n";
-
#define DRV_NAME "82596"
/* DEBUG flags
@@ -1227,8 +1224,6 @@ struct net_device * __init i82596_probe(int unit)
DEB(DEB_PROBE,printk(" IRQ %d.\n", dev->irq));
- DEB(DEB_PROBE,printk(KERN_INFO "%s", version));
-
/* The 82596-specific entries in the device structure. */
dev->open = i596_open;
dev->stop = i596_close;
--- a/drivers/net/de600.c
+++ b/drivers/net/de600.c
@@ -1,4 +1,3 @@
-static const char version[] = "de600.c: $Revision: 1.41-2.5 $, Bjorn Ekwall (bj0rn@blox.se)\n";
/*
* de600.c
*
@@ -398,9 +397,6 @@ static struct net_device * __init de600_probe(void)
}
printk(KERN_INFO "%s: D-Link DE-600 pocket adapter", dev->name);
- /* Alpha testers must have the version number to report bugs. */
- if (de600_debug > 1)
- printk(version);
/* probe for adapter */
err = -ENODEV;
--- a/drivers/net/de620.c
+++ b/drivers/net/de620.c
@@ -38,8 +35,6 @@
* Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*
*****************************************************************************/
-static const char version[] =
- "de620.c: $Revision: 1.40 $, Bjorn Ekwall <bj0rn@blox.se>\n";
/***********************************************************************
*
@@ -828,9 +823,6 @@ struct net_device * __init de620_probe(int unit)
netdev_boot_setup_check(dev);
}
- if (de620_debug)
- printk(version);
-
printk(KERN_INFO "D-Link DE-620 pocket adapter");
if (!request_region(dev->base_addr, 3, "de620")) {
next prev parent reply other threads:[~2008-06-03 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 22:06 Adrian Bunk
2008-05-22 10:09 ` Jeff Garzik
2008-06-03 18:14 ` Adrian Bunk [this message]
2008-08-05 20:44 ` Adrian Bunk
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=20080603181408.GC2663@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®