Is it okay to tag this commit with `Cc: stable@xxxxxxxxxxxxxxx` so that it'll get applied to the stable trees once merged into Linux's tree, if it's not too late? Otherwise I'll follow up on the stable merges separately. Thanks for making the changes anyway. On Thu, Nov 22, 2018 at 5:12 AM Petr Mladek <pmladek@xxxxxxxx> wrote: > > On Thu 2018-11-01 09:08:08, Petr Mladek wrote: > > On Thu 2018-11-01 10:48:21, Sergey Senozhatsky wrote: > > > On (10/31/18 13:27), Petr Mladek wrote: > > > > > > > > > > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx> > > > > > > > > The patch makes sense to me. The locks should stay busted also for > > > > console_flush_on_panic(). > > > > > > > > With the added #include <linux/vt_kern.h>: > > > > > > > > Reviewed-by: Petr Mladek <pmladek@xxxxxxxx> > > > > > > Thanks! > > > > > > Since there are no objections - how shall we route it? Via printk tree? > > > > Good question. OK, I am going to put it into printk.git unless I hear > > complains withing next couple of days. > > I have pushed this into printk.git, branch for-4.21. > > Best Regards, > Petr -- Best, Daniel
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
