From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [patch 01/10] e1000e: make E1000E default to the same kconfig setting as E1000 Date: Fri, 14 Dec 2007 18:17:55 -0500 Message-ID: <47630F23.5060403@garzik.org> References: <200712140002.lBE02pUb025505@imap1.linux-foundation.org> <4762E9FE.1070707@garzik.org> <20071214223947.GA5403@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: akpm@linux-foundation.org, netdev@vger.kernel.org, randy.dunlap@oracle.com, auke-jan.h.kok@intel.com, Linux Kernel Mailing List To: Adrian Bunk Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:42166 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754418AbXLNXSK (ORCPT ); Fri, 14 Dec 2007 18:18:10 -0500 In-Reply-To: <20071214223947.GA5403@stusta.de> Sender: netdev-owner@vger.kernel.org List-ID: Adrian Bunk wrote: > On Fri, Dec 14, 2007 at 03:39:26PM -0500, Jeff Garzik wrote: >> akpm@linux-foundation.org wrote: >>> From: Randy Dunlap >> ... >> So I think the breakage that occurs is mitigated by two factors: >> 1) kernel hackers that do their own configs are expected to be able to >> figure this stuff. >> 2) kernel builders (read: distros, mainly) are expected to have put thought >> into the Kconfig selection and driver migration strategies. >> ... >> I would prefer simply to communicate to kernel experts and builders about a >> Kconfig issue that could potentially their booting/networking... because >> this patch is only needed if the kernel experts do not already know about a >> necessary config update. > > You miss the vast majority of kconfig users: > > 3) system administrators etc. who for different reasons compile their > own kernels but neither are nor want to be kernel developers > > There's a reason why e.g. LPI requires you to be able to compile your > own kernel even for getting a "Junior Level Linux Professional" > certificate. Great! > Or that one of the authors of "Linux Device drivers" has written a book > covering only how to build and run your own kernel. Nonetheless, it will always be true that configuring your own kernel requires knowledge of the options you are setting. Jeff