From: Andrew Morton <akpm@linux-foundation.org>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
jkosina@suse.com, Geert Uytterhoeven <geert@linux-m68k.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Daniel Thompson <daniel.thompson@linaro.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v4 0/4] Cleaning printk stuff in NMI context
Date: Wed, 20 Jan 2016 13:17:13 -0800 [thread overview]
Message-ID: <20160120131713.1ee848bc261feadf570274d2@linux-foundation.org> (raw)
In-Reply-To: <1449840052-10491-1-git-send-email-pmladek@suse.com>
On Fri, 11 Dec 2015 14:20:48 +0100 Petr Mladek <pmladek@suse.com> wrote:
> this is just a quick respin of the previous version. It changes
> the few details as you suggested. Also it fixes the build problem
> on ARM as reported by Geert and Arnd.
>
> I rather send the whole patch set because there is the renamed header.
> Also the extra blank space affects two patches. I hope that it will
> safe you some work. Please, let me know if you would prefer
> incremental patches.
>
>
> Changes against v3:
>
> + used size_t for "len" and "size"
>
> + replaced WARN() with pr_err()
>
> + renamed kernel/printk/printk.h -> internal.h
>
> + fixed build on ARM (undefined NMI_LOG_BUF_SHIFT)
So the review of the v3 patchset was ... inconclusive. And everyone has
gone quiet about v4.
Probably because you didn't cc the V3 discussion participants when
sending out V4. Big mistake, sorry, I can't check everything!
But v4 is basically unaltered from v3 so can we please rev this up
again? yay or nay? Thanks.
next prev parent reply other threads:[~2016-01-20 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:20 [PATCH v4 0/4] Cleaning printk stuff in NMI context Petr Mladek
2015-12-11 13:20 ` [PATCH v4 1/4] printk/nmi: Generic solution for safe printk in NMI Petr Mladek
2015-12-11 13:20 ` [PATCH v4 2/4] printk/nmi: Use IRQ work only when ready Petr Mladek
2015-12-11 13:20 ` [PATCH v4 3/4] printk/nmi: Warn when some message has been lost in NMI context Petr Mladek
2015-12-11 13:20 ` [PATCH v4 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable Petr Mladek
2015-12-11 13:31 ` [PATCH v4 0/4] Cleaning printk stuff in NMI context Petr Mladek
2016-01-20 21:17 ` Andrew Morton [this message]
2016-01-21 11:30 ` Petr Mladek
2016-02-08 16:38 ` Petr Mladek
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=20160120131713.1ee848bc261feadf570274d2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=geert@linux-m68k.org \
--cc=jkosina@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).