From: Andrew Morton <akpm@linux-foundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: mm-commits@vger.kernel.org, zokeefe@google.com,
xiehuan09@gmail.com, wangkefeng.wang@huawei.com,
songmuchun@bytedance.com, shy828301@gmail.com,
ryan.roberts@arm.com, peterx@redhat.com, minchan@kernel.org,
mhocko@suse.com, fengwei.yin@intel.com, 21cnbao@gmail.com,
ioworker0@gmail.com
Subject: Re: [merged mm-stable] mm-madvise-optimize-lazyfreeing-with-mthp-in-madvise_free.patch removed from -mm tree
Date: Tue, 7 May 2024 10:33:23 -0700 [thread overview]
Message-ID: <20240507103323.9bfe1c3e2a83f66533db8179@linux-foundation.org> (raw)
In-Reply-To: <a0397765-ffac-4422-b82d-2f3460d6f9f8@redhat.com>
On Tue, 7 May 2024 18:54:09 +0200 David Hildenbrand <david@redhat.com> wrote:
> >
> >> Review is still going on, can we still remove that from mm-stable?
> >
> > I can rebase if needed. Is there a reason to do so? Nothing that
> > can't be fixed up with followup patches?
>
> This here is good to go and saw sufficient review. [1] was too fast for
> my taste, but it's up to you to decide if we want to fix that up piece
> by piece as more review happens.
>
OK.
Both series are cleanly droppable. Maybe drop the later series
"Reclaim lazyfree THP without splitting" - let's see what the required
fixups look like?
prev parent reply other threads:[~2024-05-07 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 0:57 [merged mm-stable] mm-madvise-optimize-lazyfreeing-with-mthp-in-madvise_free.patch removed from -mm tree Andrew Morton
2024-05-07 8:15 ` David Hildenbrand
2024-05-07 15:55 ` Andrew Morton
2024-05-07 16:54 ` David Hildenbrand
2024-05-07 17:33 ` 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=20240507103323.9bfe1c3e2a83f66533db8179@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=21cnbao@gmail.com \
--cc=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=ioworker0@gmail.com \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=wangkefeng.wang@huawei.com \
--cc=xiehuan09@gmail.com \
--cc=zokeefe@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).