From: Joe Perches <joe@perches.com>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
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: Fri, 19 Dec 2014 14:49:05 -0800 [thread overview]
Message-ID: <1419029345.25129.16.camel@perches.com> (raw)
In-Reply-To: <yw1xy4q4exo9.fsf@unicorn.mansr.com>
On Fri, 2014-12-19 at 10:33 +0000, Måns Rullgård wrote:
> Joe Perches <joe@perches.com> writes:
> > 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().
That's the general idea actually.
Dunno if that's possible at one go though.
cheers, Joe
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
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: Fri, 19 Dec 2014 14:49:05 -0800 [thread overview]
Message-ID: <1419029345.25129.16.camel@perches.com> (raw)
In-Reply-To: <yw1xy4q4exo9.fsf@unicorn.mansr.com>
On Fri, 2014-12-19 at 10:33 +0000, Måns Rullgård wrote:
> Joe Perches <joe@perches.com> writes:
> > 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().
That's the general idea actually.
Dunno if that's possible at one go though.
cheers, Joe
next prev parent reply other threads:[~2014-12-19 22:49 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 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-17 21:30 ` Kevin Cernekee
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
2014-12-19 1:43 ` Måns Rullgård
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 [this message]
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:14 ` Joe Perches
2014-12-18 23:33 ` Thomas Gleixner
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=1419029345.25129.16.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=mans@mansr.com \
--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.