From: Andrew Morton <akpm@linux-foundation.org>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: Yang Shi <shy828301@gmail.com>,
kirill.shutemov@linux.intel.com, kirill@shutemov.name,
tongtiangen@huawei.com, tony.luck@intel.com,
naoya.horiguchi@nec.com, linmiaohe@huawei.com,
linux-mm@kvack.org, osalvador@suse.de,
wangkefeng.wang@huawei.com, stevensd@chromium.org,
hughd@google.com
Subject: Re: [PATCH v12 0/3] Memory poison recovery in khugepaged collapsing
Date: Thu, 6 Apr 2023 14:56:36 -0700 [thread overview]
Message-ID: <20230406145636.a3201bf8f10e0984f861bb07@linux-foundation.org> (raw)
In-Reply-To: <CACw3F504SUuzOkcgB8ZOT9vmAkyQ8nrthvRcVwnrb+ntK3-Vsw@mail.gmail.com>
On Thu, 6 Apr 2023 11:12:14 -0700 Jiaqi Yan <jiaqiyan@google.com> wrote:
> On Tue, Apr 4, 2023 at 8:57 PM Yang Shi <shy828301@gmail.com> wrote:
> >
> > On Tue, Apr 4, 2023 at 11:44 AM Jiaqi Yan <jiaqiyan@google.com> wrote:
> > >
> > > Friendly ping for review :)
> >
> > Both I and Hugh already gave reviewed/acked for the previous version.
> > Since there were just some minor changes so you could keep the
> > reviewed/acked from the previous version.
>
> Thanks Yang!
> Andrew, is there still anything I need to do at this point (e.g.
> resent V12 with reviewed/acked tags in commits)?
> Or are you fine with this V12 to be merged?
We're good. I'll move this series from mm-unstable into mm-stable
next week.
prev parent reply other threads:[~2023-04-06 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 15:11 Jiaqi Yan
2023-03-29 15:11 ` [PATCH v12 1/3] mm/khugepaged: recover from poisoned anonymous memory Jiaqi Yan
2023-03-29 15:11 ` [PATCH v12 2/3] mm/hwpoison: introduce copy_mc_highpage Jiaqi Yan
2023-03-29 15:11 ` [PATCH v12 3/3] mm/khugepaged: recover from poisoned file-backed memory Jiaqi Yan
2023-04-04 18:44 ` [PATCH v12 0/3] Memory poison recovery in khugepaged collapsing Jiaqi Yan
2023-04-04 19:07 ` Andrew Morton
2023-04-05 3:57 ` Yang Shi
2023-04-06 18:12 ` Jiaqi Yan
2023-04-06 21:56 ` Andrew Morton [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=20230406145636.a3201bf8f10e0984f861bb07@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jiaqiyan@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=stevensd@chromium.org \
--cc=tongtiangen@huawei.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.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