From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933468Ab3CGVlR (ORCPT ); Thu, 7 Mar 2013 16:41:17 -0500 Received: from www.linutronix.de ([62.245.132.108]:51175 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753177Ab3CGVlQ (ORCPT ); Thu, 7 Mar 2013 16:41:16 -0500 Date: Thu, 7 Mar 2013 22:41:06 +0100 (CET) From: Thomas Gleixner To: Andrew Morton cc: Paul Gortmaker , Mike Frysinger , Ingo Molnar , Randy Dunlap , linux-kernel@vger.kernel.org, Russell King , Michal Simek , Ralf Baechle , Benjamin Herrenschmidt , Paul Mundt , "David S. Miller" , Chris Metcalf , Richard Weinberger Subject: Re: [PATCH v2] early_printk: consolidate random copies of identical code In-Reply-To: <20130307133542.8bdb23612990fa25c5cc9112@linux-foundation.org> Message-ID: References: <1362683754-706-1-git-send-email-paul.gortmaker@windriver.com> <20130307112536.82288f41924a38a441cdf345@linux-foundation.org> <5138EF7F.1050003@windriver.com> <20130307133542.8bdb23612990fa25c5cc9112@linux-foundation.org> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 7 Mar 2013, Andrew Morton wrote: > On Thu, 7 Mar 2013 14:50:23 -0500 Paul Gortmaker wrote: > > > This brings up a recurring question. I was tempted to just go make > > CONFIG_EARLY_PRINTK depend on CONFIG_PRINTK, but lately I've faced > > pushback when trying to "fix" things like seeing ARM OMAP USB options > > for an x86 build[1], and GOLDFISH virt drivers being offered even > > when the end user already said no to GOLDFISH[2]. > > > > Do we want to use dependencies to reflect the real world layout of > > platforms/systems, or do we want to go the minimal dependency > > approach, where we are building sparc specific drivers on mips just > > because we can? > > > > I think the former is better from a user specific point of view, as > > the maze of Kconfig is better as a tree topology with branches that > > have clear dependencies that exclude them, versus it being a flat > > monolithic space where anything can select anything. > > > > Arguments I've heard for the latter seem to be developer centric > > (i.e forcing wider build coverage on the population as a whole, etc) > > For me personally, I really really want good compilation coverage. It > drives me bats when I merge a patch but have to jump through a series > of hoops (such as not having the appropriate cross-compiler!) to be > able to build the thing. > > otoh, offering useless stuff to non-kernel-developers has downsides > with no balancing benefit, and we really should optimise things for > our users because there are so many more of them than there are of us. > > I wish we could do both :( CONFIG_AKPM? Sure go ahead, and while at it could you please implement CONFIG_DO_WHAT_I_MEAN as well ? Thanks, tglx