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 08:55:26 -0700 [thread overview]
Message-ID: <20240507085526.5f4ea12e85e637dbc8e2e9df@linux-foundation.org> (raw)
In-Reply-To: <4e4a03e7-9c2e-4e23-8e76-3b2feae4ccb4@redhat.com>
On Tue, 7 May 2024 10:15:24 +0200 David Hildenbrand <david@redhat.com> wrote:
> On 06.05.24 02:57, Andrew Morton wrote:
> >
> > The quilt patch titled
> > Subject: mm/madvise: optimize lazyfreeing with mTHP in madvise_free
> > has been removed from the -mm tree. Its filename was
> > mm-madvise-optimize-lazyfreeing-with-mthp-in-madvise_free.patch
> >
> > This patch was dropped because it was merged into the mm-stable branch
> > of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> >
>
> Andrew,
>
> this series was moved to mm-stable a bit too fast for my taste.
It was nearly three weeks.
> 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?
next prev parent reply other threads:[~2024-05-07 15:55 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 [this message]
2024-05-07 16:54 ` David Hildenbrand
2024-05-07 17:33 ` Andrew Morton
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=20240507085526.5f4ea12e85e637dbc8e2e9df@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.