On Wed, Dec 26, 2018 at 09:50:44AM -0800, Deepak Singh Rawat wrote:
> On Tue, 2018-12-25 at 07:01 -0800, Thomas Hellstrom wrote:
> > On Mon, 2018-12-24 at 11:49 +0100, Daniel Vetter wrote:
> > > On Fri, Dec 21, 2018 at 8:56 PM Thomas Hellstrom <
> > > thellst...@vmware.com> wrote:
> > > > Reviewed-
On Tue, 2018-12-25 at 07:01 -0800, Thomas Hellstrom wrote:
> On Mon, 2018-12-24 at 11:49 +0100, Daniel Vetter wrote:
> > On Fri, Dec 21, 2018 at 8:56 PM Thomas Hellstrom <
> > thellst...@vmware.com> wrote:
> > > Reviewed-by: Thomas Hellstrom
> > >
> > > Daniel, Dave, could you help try to get thi
On Mon, 2018-12-24 at 11:49 +0100, Daniel Vetter wrote:
> On Fri, Dec 21, 2018 at 8:56 PM Thomas Hellstrom <
> thellst...@vmware.com> wrote:
> > Reviewed-by: Thomas Hellstrom
> >
> > Daniel, Dave, could you help try to get this patch in -next before
> > the
> > merge window. Otherwise people will
On Fri, Dec 21, 2018 at 8:56 PM Thomas Hellstrom wrote:
>
> Reviewed-by: Thomas Hellstrom
>
> Daniel, Dave, could you help try to get this patch in -next before the
> merge window. Otherwise people will start to experience random kernel
> crashes. I figure we don't want to wait until first -fixes
Reviewed-by: Thomas Hellstrom
Daniel, Dave, could you help try to get this patch in -next before the
merge window. Otherwise people will start to experience random kernel
crashes. I figure we don't want to wait until first -fixes pull with
this.
Thanks,
Thomas
On Fri, 2018-12-21 at 11:35 -0800