From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jiri Slaby <jslaby@suse.com>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [bisected] Re: tty lockdep trace
Date: Sun, 4 Jun 2017 10:32:25 +0200 [thread overview]
Message-ID: <20170604083225.GA2959@kroah.com> (raw)
In-Reply-To: <1496471632.11868.1.camel@gmx.de>
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 Nossum <vegard.nossum@oracle.com>
> Date: Thu May 11 12:18:52 2017 +0200
>
> tty: fix port buffer locking
Now reverting this. Oops, sorry, forgot to add Dave and your names to
the patch revert. The list of people who reported this was really long,
many thanks for this.
greg k-h
next prev parent reply other threads:[~2017-06-04 8:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 17:21 tty lockdep trace Dave Jones
2017-06-03 6:33 ` [bisected] " Mike Galbraith
2017-06-04 8:32 ` Greg Kroah-Hartman [this message]
2017-06-04 9:02 ` Mike Galbraith
2017-06-04 10:00 ` Vegard Nossum
2017-06-04 11:34 ` Mike Galbraith
2017-06-05 15:09 ` Alan Cox
2017-06-05 15:41 ` Mike Galbraith
2017-06-05 4:52 ` [patch] tty: fix port buffer locking V2 Mike Galbraith
2017-06-05 6:48 ` Greg Kroah-Hartman
2017-06-05 7:16 ` Mike Galbraith
2017-06-07 2:07 ` [lkp-robot] [tty] 52b03e644f: calltrace:flush_to_ldisc kernel test robot
2017-06-07 2:25 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170604083225.GA2959@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davej@codemonkey.org.uk \
--cc=efault@gmx.de \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox