linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>
Subject: Re: Linux 5.11-rc5
Date: Fri, 5 Feb 2021 07:54:55 +0100	[thread overview]
Message-ID: <YBzrv1U2SjMZTwnB@kroah.com> (raw)
In-Reply-To: <CAHk-=wg49zd_Z2V7+djV-sCVia0=Gv3GNWz6MYsa7vG16Ya5Sg@mail.gmail.com>

On Thu, Feb 04, 2021 at 10:32:56AM -0800, Linus Torvalds wrote:
> On Thu, Feb 4, 2021 at 10:19 AM Mike Rapoport <rppt@linux.ibm.com> wrote:
> >
> > 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")?
> >
> > Unfortunately, I was too optimistic and didn't take into account that this
> > commit changes the way /dev/mem sees the first page of memory.
> >
> > There were reports of slackware users about issues with lilo after upgrade
> > from 5.10.11 to 5.10.12
> 
> Ok, applied to mainline.
> 
> Greg & stable people - this is now commit 5c279c4cf206 ("Revert
> "x86/setup: don't remove E820_TYPE_RAM for pfn 0"") in my tree.
> Although maybe you just want to revert the commit in stable, rather
> than take it from upstream? Same difference.

Taking it from upstream makes it easier to track over time what happend.
I've queued it up now, thanks!

greg k-h

  reply	other threads:[~2021-02-05  6:56 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
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 [this message]
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=YBzrv1U2SjMZTwnB@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@linux.ibm.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).