On Mon, 2017-06-05 at 16:09 +0100, Alan Cox wrote:
> On Sun, 04 Jun 2017 13:34:31 +0200
> Mike Galbraith wrote:
>
> > On Sun, 2017-06-04 at 12:00 +0200, Vegard Nossum wrote:
> > >
> > > I don't know how you did it, but this passes my testing (reproducers for
> > > both the
On Mon, 2017-06-05 at 16:09 +0100, Alan Cox wrote:
> On Sun, 04 Jun 2017 13:34:31 +0200
> Mike Galbraith wrote:
>
> > On Sun, 2017-06-04 at 12:00 +0200, Vegard Nossum wrote:
> > >
> > > I don't know how you did it, but this passes my testing (reproducers for
> > > both the original issue and
On Sun, 04 Jun 2017 13:34:31 +0200
Mike Galbraith wrote:
> On Sun, 2017-06-04 at 12:00 +0200, Vegard Nossum wrote:
> >
> > I don't know how you did it, but this passes my testing (reproducers for
> > both the original issue and the lockdep splat/hang).
>
> I suppose I can sign
On Sun, 04 Jun 2017 13:34:31 +0200
Mike Galbraith wrote:
> On Sun, 2017-06-04 at 12:00 +0200, Vegard Nossum wrote:
> >
> > I don't know how you did it, but this passes my testing (reproducers for
> > both the original issue and the lockdep splat/hang).
>
> I suppose I can sign it off, see if
On Sun, 2017-06-04 at 12:00 +0200, Vegard Nossum wrote:
>
> I don't know how you did it, but this passes my testing (reproducers for
> both the original issue and the lockdep splat/hang).
I suppose I can sign it off, see if that inspires anyone to come up
with something better.
drivers/tty: Fix
On Sun, 2017-06-04 at 12:00 +0200, Vegard Nossum wrote:
>
> I don't know how you did it, but this passes my testing (reproducers for
> both the original issue and the lockdep splat/hang).
I suppose I can sign it off, see if that inspires anyone to come up
with something better.
drivers/tty: Fix
On 06/04/17 11:02, Mike Galbraith wrote:
On Sun, 2017-06-04 at 10:32 +0200, Greg Kroah-Hartman wrote:
On Sat, Jun 03, 2017 at 08:33:52AM +0200, Mike Galbraith wrote:
On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
Just hit this during a trinity run.
On 06/04/17 11:02, Mike Galbraith wrote:
On Sun, 2017-06-04 at 10:32 +0200, Greg Kroah-Hartman wrote:
On Sat, Jun 03, 2017 at 08:33:52AM +0200, Mike Galbraith wrote:
On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
Just hit this during a trinity run.
On Sun, 2017-06-04 at 10:32 +0200, Greg Kroah-Hartman wrote:
> On Sat, Jun 03, 2017 at 08:33:52AM +0200, Mike Galbraith wrote:
> > On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
> > > Just hit this during a trinity run.
> >
> > 925bb1ce47f429f69aad35876df7ecd8c53deb7e is the first bad
On Sun, 2017-06-04 at 10:32 +0200, Greg Kroah-Hartman wrote:
> On Sat, Jun 03, 2017 at 08:33:52AM +0200, Mike Galbraith wrote:
> > On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
> > > Just hit this during a trinity run.
> >
> > 925bb1ce47f429f69aad35876df7ecd8c53deb7e is the first bad
On Sat, Jun 03, 2017 at 08:33:52AM +0200, Mike Galbraith wrote:
> On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
> > Just hit this during a trinity run.
>
> 925bb1ce47f429f69aad35876df7ecd8c53deb7e is the first bad commit
> commit 925bb1ce47f429f69aad35876df7ecd8c53deb7e
> Author: Vegard
On Sat, Jun 03, 2017 at 08:33:52AM +0200, Mike Galbraith wrote:
> On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
> > Just hit this during a trinity run.
>
> 925bb1ce47f429f69aad35876df7ecd8c53deb7e is the first bad commit
> commit 925bb1ce47f429f69aad35876df7ecd8c53deb7e
> Author: Vegard
On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
> Just hit this during a trinity run.
925bb1ce47f429f69aad35876df7ecd8c53deb7e is the first bad commit
commit 925bb1ce47f429f69aad35876df7ecd8c53deb7e
Author: Vegard Nossum
Date: Thu May 11 12:18:52 2017 +0200
On Wed, 2017-05-31 at 13:21 -0400, Dave Jones wrote:
> Just hit this during a trinity run.
925bb1ce47f429f69aad35876df7ecd8c53deb7e is the first bad commit
commit 925bb1ce47f429f69aad35876df7ecd8c53deb7e
Author: Vegard Nossum
Date: Thu May 11 12:18:52 2017 +0200
tty: fix port buffer
14 matches
Mail list logo