From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk/console: Do not suppress information about dropped messages
Date: Wed, 27 Feb 2019 09:54:04 +0100 [thread overview]
Message-ID: <878sy1fw7n.fsf@linutronix.de> (raw)
In-Reply-To: <20190227083043.j6nw7t6nqulim6t7@pathway.suse.cz> (Petr Mladek's message of "Wed, 27 Feb 2019 09:30:43 +0100")
On 2019-02-27, Petr Mladek <pmladek@suse.com> wrote:
>> Imagine a situation where I am expecting a message to come, but don't
>> see it because it was dropped. But if no more non-supressed messages
>> come, I see neither the expected message nor the dropped message.
>
> Good point! There is a simple fix for this. We could print the warning
> also when all messages are proceed and we are about to leave the
> for-cycle.
Yes! That is the piece that was missing!
John Ogness
next prev parent reply other threads:[~2019-02-27 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 12:49 [PATCH] printk/console: Do not suppress information about dropped messages Petr Mladek
2019-02-26 16:26 ` John Ogness
2019-02-27 2:55 ` Sergey Senozhatsky
2019-02-27 8:12 ` John Ogness
2019-02-27 8:44 ` Sergey Senozhatsky
2019-02-27 8:30 ` Petr Mladek
2019-02-27 8:54 ` John Ogness [this message]
2019-03-04 3:33 ` Sergey Senozhatsky
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=878sy1fw7n.fsf@linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.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).