From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: akpm@linux-foundation.org, bhe@redhat.com, bp@alien8.de,
david@redhat.com, robert.shteynfeld@gmail.com,
rppt@linux.ibm.com, stable@vger.kernel.org,
torvalds@linux-foundation.org, vbabka@suse.cz
Subject: Re: FAILED: patch "[PATCH] mm/page_alloc: fix memory map initialization for descending" failed to apply to 5.10-stable tree
Date: Thu, 22 Jul 2021 16:06:11 +0200 [thread overview]
Message-ID: <YPl7U8NgmeKoP6Q1@kroah.com> (raw)
In-Reply-To: <YPWTdETYFq+MdlEL@kernel.org>
On Mon, Jul 19, 2021 at 06:00:04PM +0300, Mike Rapoport wrote:
> On Mon, Jul 19, 2021 at 08:06:22AM +0200, Greg KH wrote:
> > On Sun, Jul 18, 2021 at 08:39:23AM +0300, Mike Rapoport wrote:
> > > Hi,
> > >
> > > On Fri, Jul 16, 2021 at 08:14:28PM +0200, gregkh@linuxfoundation.org wrote:
> > > >
> > > > The patch below does not apply to the 5.10-stable tree.
> > > > If someone wants it applied there, or to any other stable or longterm
> > > > tree, then please email the backport, including the original git commit
> > > > id to <stable@vger.kernel.org>.
> > >
> > > I'm confused. I've sent a version that applied cleanly to 5.10.49:
> > >
> > > https://lore.kernel.org/stable/YOr4DMQITU8yzBNT@kernel.org
> > >
> > > and I've got an email that it was added to the stable tree and the email
> > > with the patch for stable preview:
> > >
> > > https://lore.kernel.org/lkml/20210715182623.942552790@linuxfoundation.org
> > >
> > > Was anything wrong with the patch?
> >
> > Yes, it broke the build on ia64 due to duplicated function names :(
>
> The version below takes care of compatibility with ia64 in the least
> intrusive way I could think of.
Thanks, will go queue this up now.
greg k-h
next prev parent reply other threads:[~2021-07-22 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 18:14 FAILED: patch "[PATCH] mm/page_alloc: fix memory map initialization for descending" failed to apply to 5.10-stable tree gregkh
2021-07-18 5:39 ` Mike Rapoport
2021-07-19 6:06 ` Greg KH
2021-07-19 15:00 ` Mike Rapoport
2021-07-22 14:06 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-11 11:57 gregkh
2021-07-11 13:54 ` Mike Rapoport
2021-07-15 11:08 ` Greg KH
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=YPl7U8NgmeKoP6Q1@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=david@redhat.com \
--cc=robert.shteynfeld@gmail.com \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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