[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47FF8667.7090202@nortel.com>
Date: Fri, 11 Apr 2008 09:40:23 -0600
From: "Chris Friesen" <cfriesen@...tel.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Jeff Garzik <jeff@...zik.org>,
"Kok, Auke" <auke-jan.h.kok@...el.com>,
Matthew Wilcox <matthew@....cx>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
NetDev <netdev@...r.kernel.org>,
e1000-list <e1000-devel@...ts.sourceforge.net>,
linux-pci maillist <linux-pci@...ey.karlin.mff.cuni.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
"Ronciak, John" <john.ronciak@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
Greg KH <greg@...ah.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [regression] e1000e broke e1000
Ingo Molnar wrote:
> well, your 2.6.26 plans, if i understand them correctly, is to move
> currently working PCI IDs from e1000 to e1000e, like you attempted to d
> it in v2.6.24, which Linus reverted - correct? I.e. e1000 simply wont
> support eth0 on my T60 from 2.6.26 on? That is still an incredibly
> stupid plan, and no amount of announcement on lkml will make it any less
> stupid.
It seems like you're saying that once hardware is supported by a
particular config option, it can never ever be split out to another
config option, even if it makes both drivers cleaner.
A similar situation happened when the sk98lin driver was split into skge
and sky2...I don't remember a big fuss back then. Is it just that no
major developers were using the hardware so they didn't notice?
Chris
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists