Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751512AbaLRXeB (ORCPT ); Thu, 18 Dec 2014 18:34:01 -0500 Received: from www.linutronix.de ([62.245.132.108]:60646 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751116AbaLRXd6 (ORCPT ); Thu, 18 Dec 2014 18:33:58 -0500 Date: Fri, 19 Dec 2014 00:33:49 +0100 (CET) From: Thomas Gleixner To: Joe Perches cc: linux-arch , LKML , Geert Uytterhoeven , linux-m68k , Steven Miao , Ralf Baechle , linux-mips Subject: Re: rfc: remove early_printk from a few arches? (blackfin, m68k, mips) In-Reply-To: <1418849927.28384.1.camel@perches.com> Message-ID: References: <1418849927.28384.1.camel@perches.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) 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 Wed, 17 Dec 2014, Joe Perches wrote: > It seems like early_printk can be configured into > a few architectures but also appear not to be used. > > $ git grep -w "early_printk" ... > These seem to the only uses: ... > So blackfin, m68k, and mips seems to have it possible to enable, > but also don't appear at first glance to use it, Hint: CONFIG_EARLY_PRINTK covers far more than early_printk() > Is early_printk really used by these architectures? > Should it be removed? Sure, if you have a good reason to remove working functionality. Thanks, tglx -- 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/