[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1362686711.2125.3.camel@joe-AO722>
Date: Thu, 07 Mar 2013 12:05:11 -0800
From: Joe Perches <joe@...ches.com>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Mike Frysinger <vapier@...too.org>,
Ingo Molnar <mingo@...nel.org>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Russell King <linux@....linux.org.uk>,
Michal Simek <monstr@...str.eu>,
Ralf Baechle <ralf@...ux-mips.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mundt <lethal@...ux-sh.org>,
"David S. Miller" <davem@...emloft.net>,
Chris Metcalf <cmetcalf@...era.com>,
Richard Weinberger <richard@....at>
Subject: Re: [PATCH v2] early_printk: consolidate random copies of identical
code
On Thu, 2013-03-07 at 14:50 -0500, 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@...driver.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
[]
> This brings up a recurring question. I was tempted to just go make
> CONFIG_EARLY_PRINTK depend on CONFIG_PRINTK, but lately I've faced
> pushback when trying to "fix" things like seeing ARM OMAP USB options
> for an x86 build[1], and GOLDFISH virt drivers being offered even
> when the end user already said no to GOLDFISH[2].
I think that's the right solution and I see no
obvious insurmountable downside.
http://lkml.org/lkml/2012/9/2/97
--
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