Messages in this thread | | | Date | Mon, 29 Jun 2015 18:11:40 +0200 | Subject | Re: [PATCH 3/3] printk: implement support for extended console drivers | From | Geert Uytterhoeven <> |
| |
On Mon, Jun 29, 2015 at 5:49 PM, Tejun Heo <tj@kernel.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
etc.
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |