From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.11-rc5
Date: Mon, 25 Jan 2021 12:49:39 -0800 [thread overview]
Message-ID: <CAHk-=wh23BXwBwBgPmt9h2EJztnzKKf=qr5r=B0Hr6BGgZ-QDA@mail.gmail.com> (raw)
In-Reply-To: <161160687463.28991.354987542182281928@build.alporthouse.com>
On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> Quoting Linus Torvalds (2021-01-25 01:06:40)
> > Mike Rapoport (3):
> ...
> > mm: fix initialization of struct page for holes in memory layout
>
> We have half a dozen or so different machines in CI that are silently
> failing to boot, that we believe is bisected to this patch.
That commit reverts cleanly - so if you can verify that reverting it
fixes your CI machines, I think that that's the right thing to do for
now, unless Mike can figure out some obvious "Duh!" moment from your
working dmesg.
Mike: should we perhaps revert the first patch too (commit
bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
Linus
next prev parent reply other threads:[~2021-01-25 20:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 1:06 Linux 5.11-rc5 Linus Torvalds
2021-01-25 3:48 ` Guenter Roeck
2021-01-25 3:56 ` Bhaskar Chowdhury
2021-01-25 4:06 ` Guenter Roeck
2021-01-25 4:11 ` Bhaskar Chowdhury
2021-01-25 20:34 ` Chris Wilson
2021-01-25 20:49 ` Linus Torvalds [this message]
2021-01-25 21:33 ` Mike Rapoport
2021-01-25 21:46 ` Chris Wilson
2021-01-26 9:33 ` Chris Wilson
2021-01-26 16:24 ` Mike Rapoport
2021-01-26 18:45 ` Linus Torvalds
2021-01-27 9:38 ` Greg KH
2021-02-04 18:19 ` Mike Rapoport
2021-02-04 18:32 ` Linus Torvalds
2021-02-05 6:54 ` Greg KH
2021-01-25 21:04 ` Mike Rapoport
2021-01-25 21:13 ` Chris Wilson
2021-01-26 16:37 ` Mike Rapoport
2021-01-28 21:00 ` 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='CAHk-=wh23BXwBwBgPmt9h2EJztnzKKf=qr5r=B0Hr6BGgZ-QDA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).