[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1418951658.28384.20.camel@perches.com>
Date: Thu, 18 Dec 2014 17:14:18 -0800
From: Joe Perches <joe@...ches.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: linux-arch <linux-arch@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
Steven Miao <realmz6@...il.com>,
Ralf Baechle <ralf@...ux-mips.org>,
linux-mips <linux-mips@...ux-mips.org>
Subject: Re: rfc: remove early_printk from a few arches? (blackfin, m68k,
mips)
On Fri, 2014-12-19 at 00:33 +0100, Thomas Gleixner wrote:
> 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()
I know this.
Note also I didn't specify CONFIG_EARLY_PRINTK,
just 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.
Unused.
Ideally, all direct early_printk() uses would go away.
This would just be a starting point to minimize code.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists