[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190716133534.oyau67ocjvfegkex@pathway.suse.cz>
Date: Tue, 16 Jul 2019 15:35:34 +0200
From: Petr Mladek <pmladek@...e.com>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Vincent Whitchurch <rabinv@...s.com>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
rostedt@...dmis.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] printk: Do not lose last line in kmsg buffer dump
On Sat 2019-07-13 15:03:00, Sergey Senozhatsky wrote:
> On (07/12/19 15:11), Petr Mladek wrote:
> > > Looks correct to me as well.
> > >
> > > Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@...il.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.
Thanks for your opinion.
I'll leave it for 5.4 unless there is another urgent fix that would
trigger earlier pull request.
Best Regards,
Petr
Powered by blists - more mailing lists