From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Vincent Whitchurch <rabinv@axis.com>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
sergey.senozhatsky@gmail.com, rostedt@goodmis.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] printk: Do not lose last line in kmsg buffer dump
Date: Sat, 13 Jul 2019 15:03:00 +0900 [thread overview]
Message-ID: <20190713060300.GA1038@tigerII.localdomain> (raw)
In-Reply-To: <20190712131158.5wgy5wxjtqn6uqly@pathway.suse.cz>
On (07/12/19 15:11), Petr Mladek wrote:
> > Looks correct to me as well.
> >
> > Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
>
> The patch has been committed into printk.git, branch for-5.3-fixes.
>
> I am still a bit undecided whether to send pull request the following
> week or wait for 5.4. On one hand, it is very old bug (since 3.5).
> On the other hand, I think that it was not reported/fixed earlier
> only because it was hard to notice. And loosing the very last message
> is quite pity.
My call would be - let's wait till next merge window.
-ss
next prev parent reply other threads:[~2019-07-13 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 14:29 [PATCH v2] printk: Do not lose last line in kmsg buffer dump Vincent Whitchurch
2019-07-12 8:09 ` Petr Mladek
2019-07-12 8:44 ` Vincent Whitchurch
2019-07-12 9:12 ` Petr Mladek
2019-07-12 9:22 ` Sergey Senozhatsky
2019-07-12 13:11 ` Petr Mladek
2019-07-13 6:03 ` Sergey Senozhatsky [this message]
2019-07-16 13:35 ` 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=20190713060300.GA1038@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rabinv@axis.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=vincent.whitchurch@axis.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