From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Frysinger <vapier@gentoo.org>,
Ingo Molnar <mingo@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Michal Simek <monstr@monstr.eu>,
Ralf Baechle <ralf@linux-mips.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
Chris Metcalf <cmetcalf@tilera.com>,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH v2] early_printk: consolidate random copies of identical code
Date: Thu, 7 Mar 2013 22:25:48 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1303072224290.22263@ionos> (raw)
In-Reply-To: <5138F68A.6070203@windriver.com>
On Thu, 7 Mar 2013, Paul Gortmaker wrote:
> On 13-03-07 02:25 PM, Andrew Morton wrote:
> > On Thu, 7 Mar 2013 14:15:54 -0500 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> >
> >> [v2: essentially unchanged since v1, so I've left the acked/reviewed
> >> tags. There was a compile fail[1] for a randconfig with EARLY_PRINTK=y
> >> and PRINTK=n, because the early_console struct and early_printk calls
> >> were nested within an #ifdef CONFIG_PRINTK -- moving that whole block
> >> exactly as-is to be outside the #ifdef CONFIG_PRINTK fixes the randconfig
> >> and still works for everyday sane configs too.]
> >> [1] http://marc.info/?l=linux-next&m=136219350914998&w=2
> >
> > You did this:
> >
>
> [...]
>
> > _
> >
> > Problem is, that won't fix the various compilation problems we've had.
> > See yesterday's lkml thread "linux-next: build failure after merge of
> > the final tree (akpm tree related)"
>
> Unless I'm missing something, the easy fix for that is to just
> unconditionally have an early_console, i.e. this one line change
> on top of the v2 patch:
>
> diff --git a/kernel/printk.c b/kernel/printk.c
> index 7664e49..86799bf 100644
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -120,6 +120,7 @@ struct console_cmdline
> static struct console_cmdline console_cmdline[MAX_CMDLINECONSOLES];
> static int selected_console = -1;
> static int preferred_console = -1;
> +struct console *early_console;
> int console_set_on_cmdline;
> EXPORT_SYMBOL(console_set_on_cmdline);
>
> @@ -1718,7 +1719,6 @@ static size_t cont_print_text(char *text, size_t size) { return 0; }
> #endif /* CONFIG_PRINTK */
>
> #ifdef CONFIG_EARLY_PRINTK
> -struct console *early_console;
>
> void early_vprintk(const char *fmt, va_list ap)
> {
>
>
> Then you don't have to spray any of those ifdefs into the sparc code.
Yeah, that's what I thought as well. The extra pointer is not going to
create massive bloat :)
Btw, we should put that into the read_mostly section while at it.
Thanks,
tglx
next prev parent reply other threads:[~2013-03-07 21:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 19:15 [PATCH v2] early_printk: consolidate random copies of identical code Paul Gortmaker
2013-03-07 19:25 ` Andrew Morton
2013-03-07 19:50 ` Paul Gortmaker
2013-03-07 20:05 ` Joe Perches
2013-03-07 21:35 ` Andrew Morton
2013-03-07 21:41 ` Thomas Gleixner
2013-03-07 22:47 ` Rob Landley
2013-03-08 0:49 ` Paul Gortmaker
2013-03-08 0:56 ` Andrew Morton
2013-03-08 1:15 ` Paul Gortmaker
2013-03-08 1:10 ` Steven Rostedt
2013-03-08 15:29 ` Guenter Roeck
2013-03-07 20:20 ` Paul Gortmaker
2013-03-07 21:25 ` Thomas Gleixner [this message]
2013-03-07 21:43 ` Andrew Morton
2013-03-07 22:34 ` Thomas Gleixner
2013-03-08 16:11 ` [PATCH v3] " Paul Gortmaker
2013-03-08 21:46 ` Andrew Morton
2013-03-23 21:23 ` Geert Uytterhoeven
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=alpine.LFD.2.02.1303072224290.22263@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=monstr@monstr.eu \
--cc=paul.gortmaker@windriver.com \
--cc=ralf@linux-mips.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=vapier@gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox