Re: [2.6 patch] schedule eepro100.c for removal

[Adrian Bunk <bunk@stusta.de>]

On Fri, Mar 03, 2006 at 09:24:46PM -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
> >Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> >---
> >
> >This patch was already sent on:
> >- 4 Feb 2006
> >
> > Documentation/feature-removal-schedule.txt |    6 ++++++
> > drivers/net/eepro100.c                     |    1 +
> > 2 files changed, 7 insertions(+)
> >
> >--- linux-2.6.15-mm4-full/Documentation/feature-removal-schedule.txt.old 
> >2006-01-18 08:38:57.000000000 +0100
> >+++ linux-2.6.15-mm4-full/Documentation/feature-removal-schedule.txt 
> >2006-01-18 08:39:59.000000000 +0100
> >@@ -164,0 +165,6 @@
> >+---------------------------
> >+
> >+What:   eepro100 network driver
> >+When:   August 2006
> >+Why:    replaced by the e100 driver
> >+Who:    Adrian Bunk <bunk@stusta.de>
> 
> ACK, provided you change the year to 2007
> 
> >--- linux-2.6.16-rc1-mm5-full/drivers/net/eepro100.c.old	2006-02-03 
> >23:37:55.000000000 +0100
> >+++ linux-2.6.16-rc1-mm5-full/drivers/net/eepro100.c	2006-02-03 
> >23:39:10.000000000 +0100
> >@@ -2391,6 +2391,7 @@ static int __init eepro100_init_module(v
> > #ifdef MODULE
> > 	printk(version);
> > #endif
> >+	printk(KERN_WARNING "eepro100 will be removed soon, please use the 
> >e100 driver\n");
> > 	return pci_module_init(&eepro100_driver);
> 
> NAK

Other people wanted this part of the patch...


It seems the feature-removal-schedule.txt part with a changed date is 
already part of git-netdev-all.patch in recent -mm kernels.

Do you still want me to resend it?


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/