Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760581AbYA3X6Q (ORCPT ); Wed, 30 Jan 2008 18:58:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755130AbYA3X6F (ORCPT ); Wed, 30 Jan 2008 18:58:05 -0500 Received: from smtp6.pp.htv.fi ([213.243.153.40]:52154 "EHLO smtp6.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752454AbYA3X6D (ORCPT ); Wed, 30 Jan 2008 18:58:03 -0500 Date: Thu, 31 Jan 2008 01:58:36 +0200 From: Adrian Bunk To: Linus Torvalds Cc: Randy Dunlap , Linux Kernel Mailing List , auke-jan.h.kok@intel.com, jeff@garzik.org, "David S. Miller" , akpm , netdev@vger.kernel.org Subject: Re: Mostly revert "e1000/e1000e: Move PCI-Express device IDs over to e1000e" Message-ID: <20080130235836.GV29368@does.not.exist> References: <200801292359.m0TNxb75011826@hera.kernel.org> <20080129212314.91b9bb5b.randy.dunlap@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2581 Lines: 67 On Wed, Jan 30, 2008 at 04:51:04PM +1100, Linus Torvalds wrote: > > > On Tue, 29 Jan 2008, Randy Dunlap wrote: > > > > Andrew was concerned about this when the driver was in -mm. > > He asked for a patch that would set E1000E to same value as E1000 > > and I supplied that. Auke acked it IIRC. Other people vetoed it. :( > > Yeah, I've been discussing with Jeff and the gang. > > I think we have agreed on a solution where the ID's show up in the old > driver if the new driver is not enabled at all. > > (And as a side note: it turns out that the problem I experienced didn't > come from the new e1000e driver after all, so I'll be removing the > EXPERIMENTAL flag again). > > So I'd suggest the final patch be something like this, but I'm sendign it > out just as an example of how we could solve this, not necessarily as a > final patch. > > Jeff, Auke, would something like this be acceptable? It makes it very > obvious in the driver table which entries are for the PCIE versions that > would be handled by the E1000E driver if it is enabled.. > > Untested, but as mentioned, this is more of a "this looks maintainable and > like it should solve the issues" rather than anything I was planning on > committing now. I don't like it: We should aim at having exactly one driver for one card. Your patch has effects like e.g. a kernel behaving differently when adding and compiling the e1000e module later compared to having it originally in the .config. And fun like "The card works on my machine with the e1000 driver, why doesn't it work in your machine with the e1000 driver?". And in terms of maintainability, people will disable the e1000e driver in their kernel for working around bugs in it instead of reporting the bugs. Exactly what we want to not happen. And unless we want to keep this situation forever, we anyway have to remove the support for the PCI-Express adapters from the e1000 driver at some point in time, so why not make a clear cut now? Whatever problems this causes will be the same now or in a few years. > Linus 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/