From: Greg KH <gregkh@linuxfoundation.org>
To: Naoya Horiguchi <naoya.horiguchi@linux.dev>
Cc: stable@vger.kernel.org, akpm@linux-foundation.org,
david@redhat.com, linmiaohe@huawei.com, liushixin2@huawei.com,
mike.kravetz@oracle.com, osalvador@suse.de, shy828301@gmail.com,
songmuchun@bytedance.com, naoya.horiguchi@nec.com
Subject: Re: FAILED: patch "[PATCH] mm/hugetlb: separate path for hwpoison entry in" failed to apply to 5.18-stable tree
Date: Mon, 1 Aug 2022 10:19:05 +0200 [thread overview]
Message-ID: <YueMeT1huXybhx+1@kroah.com> (raw)
In-Reply-To: <20220801062937.GA192992@ik1-406-35019.vs.sakura.ne.jp>
On Mon, Aug 01, 2022 at 03:29:37PM +0900, Naoya Horiguchi wrote:
> On Sat, Jul 30, 2022 at 05:35:37PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.18-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>.
> >
> > thanks,
>
> Hello,
>
> I updated the patch for 5.18-stable, could you apply this?
I can, but are you sure you need/want this for 5.18-stable?
I ask because of this line in the changelog text:
> Fixes: 6c287605fd56 ("mm: remember exclusively mapped anonymous pages with PG_anon_exclusive")
Which only showed up in 5.19-rc1 and is not backported anywhere.
So why did you have:
> Cc: <stable@vger.kernel.org> [5.18]
In the changelog if the commit this fixes is not in 5.18?
confused,
greg k-h
next prev parent reply other threads:[~2022-08-01 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 15:35 FAILED: patch "[PATCH] mm/hugetlb: separate path for hwpoison entry in" failed to apply to 5.18-stable tree gregkh
2022-08-01 6:29 ` Naoya Horiguchi
2022-08-01 8:19 ` Greg KH [this message]
2022-08-01 8:32 ` HORIGUCHI NAOYA(堀口 直也)
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=YueMeT1huXybhx+1@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=liushixin2@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@linux.dev \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.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