From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Petr Mladek <pmladek@suse.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jiri Kosina <jkosina@suse.com>, Cris <linux-cris-kernel@axis.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
the arch/x86 maintainers <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
"adi-buildroot-devel@lists.sourceforge.net"
<adi-buildroot-devel@lists.sourceforge.net>,
Ingo Molnar <mingo@redhat.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
sparclinux <sparclinux@vger.kernel.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable
Date: Fri, 11 Dec 2015 13:47:59 +0100 [thread overview]
Message-ID: <10841284.ycX60MmRhF@wuerfel> (raw)
In-Reply-To: <20151211124159.GB3729@pathway.suse.cz>
On Friday 11 December 2015 13:41:59 Petr Mladek wrote:
> diff --git a/init/Kconfig b/init/Kconfig
> index efcff25a112d..61cfd96a3c96 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -870,7 +870,7 @@ config NMI_LOG_BUF_SHIFT
> int "Temporary per-CPU NMI log buffer size (12 => 4KB, 13 => 8KB)"
> range 10 21
> default 13
> - depends on PRINTK && HAVE_NMI
> + depends on PRINTK_NMI
> help
> Select the size of a per-CPU buffer where NMI messages are temporary
> stored. They are copied to the main log buffer in a safe context
>
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
I found this on linux-next as well today and came to the same conclusion.
Arnd
next prev parent reply other threads:[~2015-12-11 12:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 13:21 [PATCH v3 0/4] Cleaning printk stuff in NMI context Petr Mladek
2015-12-09 13:21 ` [PATCH v3 1/4] printk/nmi: Generic solution for safe printk in NMI Petr Mladek
2015-12-09 23:50 ` Andrew Morton
2015-12-10 15:26 ` Petr Mladek
2015-12-09 13:21 ` [PATCH v3 2/4] printk/nmi: Use IRQ work only when ready Petr Mladek
2015-12-09 13:21 ` [PATCH v3 3/4] printk/nmi: Warn when some message has been lost in NMI context Petr Mladek
2015-12-09 13:21 ` [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable Petr Mladek
2015-12-11 11:10 ` Geert Uytterhoeven
2015-12-11 11:10 ` Geert Uytterhoeven
2015-12-11 12:41 ` Petr Mladek
2015-12-11 12:41 ` Petr Mladek
2015-12-11 12:47 ` Arnd Bergmann [this message]
2015-12-11 12:47 ` Arnd Bergmann
2015-12-11 12:50 ` Geert Uytterhoeven
2015-12-11 12:50 ` Geert Uytterhoeven
2015-12-11 22:57 ` Andrew Morton
2015-12-11 22:57 ` Andrew Morton
2015-12-11 23:21 ` Russell King - ARM Linux
2015-12-11 23:21 ` Russell King - ARM Linux
2015-12-11 23:26 ` Jiri Kosina
2015-12-11 23:26 ` Jiri Kosina
2015-12-18 10:18 ` Daniel Thompson
2015-12-18 10:18 ` Daniel Thompson
2015-12-18 11:29 ` Peter Zijlstra
2015-12-18 11:29 ` Peter Zijlstra
2015-12-18 12:11 ` Peter Zijlstra
2015-12-18 12:11 ` Peter Zijlstra
2015-12-18 23:03 ` Andrew Morton
2015-12-18 23:03 ` Andrew Morton
2015-12-18 14:52 ` Petr Mladek
2015-12-18 14:52 ` Petr Mladek
2015-12-18 17:00 ` Daniel Thompson
2015-12-18 17:00 ` Daniel Thompson
2016-03-01 14:04 ` Daniel Thompson
2016-03-01 14:04 ` Daniel Thompson
2015-12-11 23:30 ` Andrew Morton
2015-12-11 23:30 ` Andrew Morton
2015-12-15 14:26 ` Petr Mladek
2015-12-15 14:26 ` Petr Mladek
2015-12-17 22:38 ` Andrew Morton
2015-12-17 22:38 ` Andrew Morton
2015-12-18 16:18 ` Petr Mladek
2015-12-18 16:18 ` Petr Mladek
2015-12-14 10:28 ` Daniel Thompson
2015-12-14 10:28 ` Daniel Thompson
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=10841284.ycX60MmRhF@wuerfel \
--to=arnd@arndb.de \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=akpm@linux-foundation.org \
--cc=daniel.thompson@linaro.org \
--cc=geert@linux-m68k.org \
--cc=jkosina@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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