From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "Huang, Ying" <ying.huang@intel.com>,
"mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
"songmuchun@bytedance.com" <songmuchun@bytedance.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Revert "mm: migration: fix the FOLL_GET failure on following huge page"
Date: Wed, 9 Nov 2022 11:36:45 +0000 [thread overview]
Message-ID: <BYAPR11MB34957E86BA5A3CE0B72C06DBF73E9@BYAPR11MB3495.namprd11.prod.outlook.com> (raw)
In-Reply-To: <496786039852aba90ffa68f10d0df3f4236a990b.1667983080.git.baolin.wang@linux.alibaba.com>
> -----Original Message-----
> From: Baolin Wang <baolin.wang@linux.alibaba.com>
> Sent: Wednesday, November 9, 2022 16:40
> To: akpm@linux-foundation.org
> Cc: Wang, Haiyue <haiyue.wang@intel.com>; Huang, Ying <ying.huang@intel.com>; mike.kravetz@oracle.com;
> songmuchun@bytedance.com; baolin.wang@linux.alibaba.com; linux-mm@kvack.org; linux-
> kernel@vger.kernel.org
> Subject: [PATCH] Revert "mm: migration: fix the FOLL_GET failure on following huge page"
>
> Revert commit 831568214883 ("mm: migration: fix the FOLL_GET failure on
> following huge page"), since after commit 1a6baaa0db73 ("s390/hugetlb:
> switch to generic version of follow_huge_pud()") and commit 57a196a58421
> ("hugetlb: simplify hugetlb handling in follow_page_mask") were merged,
> now all the following huge page routines can support FOLL_GET operation.
>
> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> ---
Cool, thanks, my ugly code is gone. ;-)
Acked-by: Haiyue Wang <haiyue.wang@intel.com>
> mm/migrate.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> --
> 1.8.3.1
prev parent reply other threads:[~2022-11-09 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 8:40 Baolin Wang
2022-11-09 11:36 ` Wang, Haiyue [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=BYAPR11MB34957E86BA5A3CE0B72C06DBF73E9@BYAPR11MB3495.namprd11.prod.outlook.com \
--to=haiyue.wang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=songmuchun@bytedance.com \
--cc=ying.huang@intel.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