From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756352AbYDITul (ORCPT ); Wed, 9 Apr 2008 15:50:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754285AbYDITua (ORCPT ); Wed, 9 Apr 2008 15:50:30 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:38897 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754059AbYDITu3 (ORCPT ); Wed, 9 Apr 2008 15:50:29 -0400 Message-ID: <47FD1DF6.2000007@garzik.org> Date: Wed, 09 Apr 2008 15:50:14 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Ingo Molnar CC: Matthew Wilcox , "Kok, Auke" , 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: [patch] e1000=y && e1000e=m regression fix 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> <47FBD34A.6080508@garzik.org> <20080408203314.GA28952@elte.hu> <47FBDBE9.9040700@garzik.org> <20080409193850.GA11763@elte.hu> In-Reply-To: <20080409193850.GA11763@elte.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.2.4 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ingo Molnar wrote: > * Jeff Garzik wrote: > >>> We've got three thousand Kconfig options - it is clearly not >>> realistic for users to keep such details in mind to avoid pitfalls. >> Agreed -- hence the multiple announcements, including in this thread, >> to put said details into mind. > > which part of "it took a kernel developer more than an hour to figure > out why his laptop had a dead network interface" did you not understand? > Whatever you did, it was not apparent to me. I dont follow every tiny > detail of the e1000 driver family, nor do 99%+ [*] of our users. You do follow LKML, where multiple announcements have and are being posted. Jeff