From: Joe Perches <joe@perches.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arch <linux-arch@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Steven Miao <realmz6@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: rfc: remove early_printk from a few arches? (blackfin, m68k, mips)
Date: Thu, 18 Dec 2014 17:14:18 -0800 [thread overview]
Message-ID: <1418951658.28384.20.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1412190031530.17382@nanos>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arch <linux-arch@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k <linux-m68k@vger.kernel.org>,
Steven Miao <realmz6@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: rfc: remove early_printk from a few arches? (blackfin, m68k, mips)
Date: Thu, 18 Dec 2014 17:14:18 -0800 [thread overview]
Message-ID: <1418951658.28384.20.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1412190031530.17382@nanos>
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.
next prev parent reply other threads:[~2014-12-19 1:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:58 rfc: remove early_printk from a few arches? (blackfin, m68k, mips) Joe Perches
2014-12-17 20:58 ` Joe Perches
2014-12-17 21:30 ` Kevin Cernekee
2014-12-17 21:30 ` Kevin Cernekee
2014-12-17 21:30 ` Kevin Cernekee
2014-12-17 22:30 ` Måns Rullgård
2014-12-17 22:30 ` Måns Rullgård
2014-12-17 22:30 ` Måns Rullgård
2014-12-18 23:33 ` Thomas Gleixner
2014-12-18 23:33 ` Thomas Gleixner
2014-12-18 23:33 ` Thomas Gleixner
2014-12-19 1:14 ` Joe Perches
2014-12-19 1:14 ` Joe Perches [this message]
2014-12-19 1:14 ` Joe Perches
2014-12-19 1:43 ` Måns Rullgård
2014-12-19 1:43 ` Måns Rullgård
2014-12-19 2:08 ` Joe Perches
2014-12-19 2:08 ` Joe Perches
2014-12-19 10:33 ` Måns Rullgård
2014-12-19 10:33 ` Måns Rullgård
2014-12-19 22:49 ` Joe Perches
2014-12-19 22:49 ` Joe Perches
2014-12-28 18:36 ` Pavel Machek
2014-12-28 18:36 ` Pavel Machek
2014-12-19 1:43 ` Måns Rullgård
2014-12-19 8:03 ` Geert Uytterhoeven
2014-12-19 8:03 ` Geert Uytterhoeven
2014-12-19 8:03 ` Geert Uytterhoeven
2014-12-28 18:33 ` Pavel Machek
2014-12-28 18:33 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2014-12-17 20:58 Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1418951658.28384.20.camel@perches.com \
--to=joe@perches.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=realmz6@gmail.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.