From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, Jonathan Corbet <corbet@lwn.net>,
x86 <x86@kernel.org>, William Grant <william.grant@canonical.com>,
Woody Suwalski <terraluna977@gmail.com>
Subject: Re: Linux 4.16: Reported regressions as of Monday, 2018-02-26 (Was: Linux 4.16-rc3)
Date: Tue, 27 Feb 2018 12:21:48 +0100 [thread overview]
Message-ID: <1585962.fYXxTULH6v@aspire.rjw.lan> (raw)
In-Reply-To: <2cf45d87-066c-7368-3fbd-20675f2d74ae@leemhuis.info>
On Monday, February 26, 2018 11:25:09 AM CET Thorsten Leemhuis wrote:
> On 26.02.2018 04:05, Linus Torvalds wrote:
> > We're on the normal schedule for 4.16 and everything still looks very regular.
>
> Hi! Find below my second regression report for Linux 4.16. It lists 8
> regressions I'm currently aware of.
>
> To anyone reading this: Are you aware of any other regressions that got
> introduced this development cycle? Then please let me know by mail (a
> simple bounce or forward to the email address is enough!).
>
> For details see http://bit.ly/lnxregtrackid And please tell me if there
> is anything in the report that shouldn't be there.
Please add https://bugzilla.kernel.org/show_bug.cgi?id=198763
It has a bisect result and seems to be readily reproducible.
No response from the author of the problematic commit so far.
Thanks,
Rafael
next prev parent reply other threads:[~2018-02-27 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 3:05 Linux 4.16-rc3 Linus Torvalds
2018-02-26 10:25 ` Linux 4.16: Reported regressions as of Monday, 2018-02-26 (Was: Linux 4.16-rc3) Thorsten Leemhuis
2018-02-27 11:21 ` Rafael J. Wysocki [this message]
2018-03-08 11:40 ` Pavel Machek
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=1585962.fYXxTULH6v@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=regressions@leemhuis.info \
--cc=terraluna977@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=william.grant@canonical.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®