[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180628090810.GA2286@jagdpanzerIV>
Date: Thu, 28 Jun 2018 18:08:10 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v2 0/3] printk: Deadlock in NMI regression
On (06/27/18 16:34), Petr Mladek wrote:
[..]
> > > Changes against v1:
> > >
> > > + Move the check from vprintk_emit() to vprintk_func()
> > > + More straightforward commit message
> > > + Fix build with CONFIG_PRINTK_NMI disabled
> >
> > Did I miss out V1?
>
> It is the above fixed link. I am sorry for the confusion.
Ah, yep.
[..]
> Ah, the following line somehow confused git send-mail and the message
> had broken list of recipients:
>
> Cc: stable@...r.kernel.org # 4.13+
>
> I have sent it once again as you have already noticed.
Got it. Happened to me before as well. I asked because I sort of have
some suspicion that lkml email deliver has not been completely reliable
lately.
-ss
Powered by blists - more mailing lists