From: Marco Elver <elver@google.com>
To: Petr Mladek <pmladek@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Vlastimil Babka <vbabka@suse.cz>, Timur Tabi <timur@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH 1/2] lib/vsprintf: do not show no_hash_pointers message multiple times
Date: Wed, 17 Mar 2021 20:34:43 +0100 [thread overview]
Message-ID: <CANpmjNMYoQ-xE9HY+DH+wO3BSGsuOjCxffchzUhuxWk4zhf3Yw@mail.gmail.com> (raw)
In-Reply-To: <YEX15gn0lfDpc1dw@alley>
On Mon, 8 Mar 2021 at 11:01, Petr Mladek <pmladek@suse.com> wrote:
> On Fri 2021-03-05 20:42:05, Marco Elver wrote:
> > Do not show no_hash_pointers message multiple times if the option was
> > passed more than once (e.g. via generated command line).
> >
> > Signed-off-by: Marco Elver <elver@google.com>
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
Could you pick up this patch only?
I think there's still controversy around how to best proceed with
reducing space and we should drop patch 2/2 for now.
If you'd like me to re-send this standalone I can do so as well.
Thanks,
-- Marco
next prev parent reply other threads:[~2021-03-17 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 19:42 [PATCH 1/2] lib/vsprintf: do not show no_hash_pointers message multiple times Marco Elver
2021-03-05 19:42 ` [PATCH 2/2] lib/vsprintf: reduce space taken by no_hash_pointers warning Marco Elver
2021-03-06 20:27 ` Timur Tabi
2021-03-08 10:16 ` Petr Mladek
2021-03-08 10:51 ` Marco Elver
2021-03-12 3:46 ` Timur Tabi
2021-03-08 12:22 ` Geert Uytterhoeven
2021-03-08 17:23 ` Petr Mladek
2021-03-08 18:23 ` Marco Elver
2021-03-08 18:36 ` Andy Shevchenko
2021-03-09 9:12 ` David Laight
2021-03-08 10:33 ` Andy Shevchenko
2021-03-08 10:01 ` [PATCH 1/2] lib/vsprintf: do not show no_hash_pointers message multiple times Petr Mladek
2021-03-17 19:34 ` Marco Elver [this message]
2021-03-19 10:40 ` 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=CANpmjNMYoQ-xE9HY+DH+wO3BSGsuOjCxffchzUhuxWk4zhf3Yw@mail.gmail.com \
--to=elver@google.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=timur@kernel.org \
--cc=vbabka@suse.cz \
/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).