From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760944AbYDKPla (ORCPT ); Fri, 11 Apr 2008 11:41:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760132AbYDKPlM (ORCPT ); Fri, 11 Apr 2008 11:41:12 -0400 Received: from zrtps0kp.nortel.com ([47.140.192.56]:55329 "EHLO zrtps0kp.nortel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760086AbYDKPlK (ORCPT ); Fri, 11 Apr 2008 11:41:10 -0400 Message-ID: <47FF8667.7090202@nortel.com> Date: Fri, 11 Apr 2008 09:40:23 -0600 From: "Chris Friesen" User-Agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ingo Molnar CC: Jeff Garzik , "Kok, Auke" , Matthew Wilcox , Linux Kernel Mailing List , NetDev , e1000-list , linux-pci maillist , Andrew Morton , "David S. Miller" , Linus Torvalds , Jesse Brandeburg , "Ronciak, John" , "Allan, Bruce W" , Greg KH , Arjan van de Ven , "Rafael J. Wysocki" Subject: Re: [regression] e1000e broke e1000 References: <20080408083606.GA20863@elte.hu> <47FB9ABB.9080403@intel.com> <20080408183921.GA20803@elte.hu> <20080408193245.GG11962@parisc-linux.org> <20080408195123.GA28148@elte.hu> <47FBCE00.2020309@garzik.org> <20080408200652.GC28148@elte.hu> <47FBD620.1080508@intel.com> <20080409191256.GB9276@elte.hu> <47FD19F5.9020509@garzik.org> <20080411113018.GD9205@elte.hu> In-Reply-To: <20080411113018.GD9205@elte.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Apr 2008 15:40:29.0367 (UTC) FILETIME=[5EB59470:01C89BEA] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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