All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Mike Rapoport <rppt@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.11-rc5
Date: Tue, 26 Jan 2021 09:33:39 +0000	[thread overview]
Message-ID: <161165361960.29150.15515544628767131483@build.alporthouse.com> (raw)
In-Reply-To: <161161117911.29150.13853544418926100149@build.alporthouse.com>

Quoting Chris Wilson (2021-01-25 21:46:19)
> Quoting Mike Rapoport (2021-01-25 21:33:48)
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
> > 
> > I wonder, maybe actually this one is causing troubles?
> > 
> > Chris, would it be possible to check what happens if you revert only
> > bde9cfa3afe4?
> 
> Queued for CI, will be run in about an hour.

I ran just the revert of bde9cfa3afe4 through CI twice, on both occasions
all machines failed to boot. 
-Chris

  reply	other threads:[~2021-01-26 15:20 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
2021-01-25 21:33     ` Mike Rapoport
2021-01-25 21:46       ` Chris Wilson
2021-01-26  9:33         ` Chris Wilson [this message]
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=161165361960.29150.15515544628767131483@build.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@linux.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.