From: Greg KH <gregkh@linuxfoundation.org>
To: "Alan J. Wylie" <alan@wylie.me.uk>
Cc: Alec Ari <neotheuser@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [Regression] Re: Linux 5.0.2
Date: Thu, 14 Mar 2019 14:59:01 -0700 [thread overview]
Message-ID: <20190314215901.GA19535@kroah.com> (raw)
In-Reply-To: <20190314215250.GB17893@kroah.com>
On Thu, Mar 14, 2019 at 02:52:50PM -0700, Greg KH wrote:
> On Thu, Mar 14, 2019 at 08:43:14PM +0000, Alan J. Wylie wrote:
> >
> > (Adding Linus, since his tree is also broken)
>
> Again, can you try running 'git bisect' to find the offending commit?
Ah, looks like Guenter found it, nevermind...
next prev parent reply other threads:[~2019-03-14 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 16:27 Linux 5.0.2 Greg KH
2019-03-14 16:28 ` Greg KH
[not found] ` <87pnqtkz23.fsf@wylie.me.uk>
2019-03-14 20:07 ` [Regression] " Greg KH
2019-03-14 20:43 ` Alan J. Wylie
2019-03-14 21:52 ` Greg KH
2019-03-14 21:59 ` Greg KH [this message]
2019-03-14 22:16 ` Alan J. Wylie
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=20190314215901.GA19535@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@wylie.me.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=neotheuser@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).