public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: aarcange@redhat.com, akpm@linux-foundation.org, dbueso@suse.de,
	joao.m.martins@oracle.com, kirill.shutemov@linux.intel.com,
	osalvador@suse.de, stable@vger.kernel.org,
	torvalds@linux-foundation.org, willy@infradead.org,
	ziy@nvidia.com
Subject: Re: FAILED: patch "[PATCH] hugetlb: fix update_and_free_page contig page struct" failed to apply to 4.19-stable tree
Date: Thu, 4 Mar 2021 14:36:52 +0100	[thread overview]
Message-ID: <YEDidFjy2b5Jw/uU@kroah.com> (raw)
In-Reply-To: <4712beaf-1714-e19c-32a0-ca76d398961e@oracle.com>

On Mon, Mar 01, 2021 at 08:24:43PM -0800, Mike Kravetz wrote:
> On 3/1/21 4:41 AM, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.19-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>.
> 
> 
> >From b6dec027a8967feb788e14f3bbd57f318005001f Mon Sep 17 00:00:00 2001
> From: Mike Kravetz <mike.kravetz@oracle.com>
> Date: Mon, 1 Mar 2021 18:12:38 -0800
> Subject: [PATCH] hugetlb: fix update_and_free_page contig page struct
>  assumption
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> commit dbfee5aee7e54f83d96ceb8e3e80717fac62ad63 upstream.

Queued up everywhere, thanks.

greg k-h

      reply	other threads:[~2021-03-04 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 12:41 FAILED: patch "[PATCH] hugetlb: fix update_and_free_page contig page struct" failed to apply to 4.19-stable tree gregkh
2021-03-02  4:24 ` Mike Kravetz
2021-03-04 13:36   ` Greg KH [this message]

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=YEDidFjy2b5Jw/uU@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dbueso@suse.de \
    --cc=joao.m.martins@oracle.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=mike.kravetz@oracle.com \
    --cc=osalvador@suse.de \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    --cc=ziy@nvidia.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