[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150629161355.GS15805@mtj.duckdns.org>
Date: Mon, 29 Jun 2015 12:13:55 -0400
From: Tejun Heo <tj@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: pmladek@...e.cz, Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Kay Sievers <kay@...y.org>,
Josh Triplett <josh@...htriplett.org>,
Linux Embedded <linux-embedded@...r.kernel.org>
Subject: Re: [PATCH 3/3] printk: implement support for extended console
drivers
On Mon, Jun 29, 2015 at 06:11:40PM +0200, Geert Uytterhoeven wrote:
> On Mon, Jun 29, 2015 at 5:49 PM, Tejun Heo <tj@...nel.org> wrote:
> > On Mon, Jun 29, 2015 at 05:47:49PM +0200, Geert Uytterhoeven wrote:
> >> > netconsole itself is optional & modular. I'm not sure making further
> >> > splits is called for, especially given the use cases.
> >>
> >> It could be a hidden option, selected by its users (e.g. netconsole).
> >
> > Hmmm... what do you mean?
>
> init/Kconfig:
>
> config PRINTK_EXT_LOG
> bool
>
> drivers/net/Kconfig:
>
> config NETCONSOLE
> tristate "Network console logging support"
> select PRINTK_EXT_LOG
>
> kernel/printk/printk.c:
>
> void console_unlock(void)
> {
> #ifdef CONFIG_PRINTK_EXT_LOG
> static char ext_text[CONSOLE_EXT_LOG_MAX];
> #endif
OIC, hmmm... yeah, I think doing it on-demand would be better but will
try to find out which way is better.
Thanks!
--
tejun
--
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