From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= Subject: Re: rfc: remove early_printk from a few arches? (blackfin, m68k, mips) Date: Fri, 19 Dec 2014 10:33:42 +0000 Message-ID: References: <1418849927.28384.1.camel@perches.com> <1418951658.28384.20.camel@perches.com> <1418954914.25129.1.camel@perches.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <1418954914.25129.1.camel@perches.com> (Joe Perches's message of "Thu, 18 Dec 2014 18:08:34 -0800") Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Joe Perches Cc: Thomas Gleixner , linux-arch , LKML , Geert Uytterhoeven , linux-m68k , Steven Miao , Ralf Baechle , linux-mips Joe Perches writes: > On Fri, 2014-12-19 at 01:43 +0000, M=E5ns Rullg=E5rd wrote: >> What exactly are you proposing to remove? > > Optionally compile out > kernel/printk/printk.c:early_printk() > even if CONFIG_EARLY_PRINTK is enabled. > >> I see no unused code related >> to early printk (in any variant) under arch/mips. > > I think there could be yet another CONFIG option > to specifically enable the early_printk function > for the arches that use it. Why bother? On MIPS it would save 132 bytes of compiled code. > The kernel/printk/early_printk() function seems > used only by arm/microblaze/tile/x86. Rather than introduce more config complexity, you could try to remove the 7 remaining uses of early_printk(). - arch/arm/mach-socfpga Single early_printk("Early printk initialized\n") call serving no apparent purpose can probably be safely deleted. Since there are no other early_printk() calls, this information seems rather useless. - arch/microblaze, arch/tile, arch/x86 These all do a register_console() for the early console, so regular printk() should work. Moreover, x86 allows multiple early consoles, but calling early_printk() will only output to the last one specified= =2E --=20 M=E5ns Rullg=E5rd mans@mansr.com