From: Andrew Morton <akpm@linux-foundation.org>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: vishal.moola@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Ye Liu <ye.liu@linux.dev>,
Zhen Ni <zhen.ni@easystack.cn>
Subject: Re: [PATCH v4 0/2] tools/mm/page_owner_sort: split filter cleanup and allocation fix
Date: Wed, 24 Jun 2026 21:15:44 -0700 [thread overview]
Message-ID: <20260624211544.8437baec5054d079e7ea30f0@linux-foundation.org> (raw)
In-Reply-To: <16E1A77F98E4C49E+20260616055401.1570629-1-chenyichong@uniontech.com>
On Tue, 16 Jun 2026 13:53:59 +0800 Yichong Chen <chenyichong@uniontech.com> wrote:
> Split the v3 change into two patches as suggested by Vishal.
>
> Patch 1 renames is_need() to filter_record() and makes the filter path
> return explicit results. Patch 2 fixes the per-record allocation leaks.
Thanks.
We're now at -rc1 (almost), so expect people to start paying more
attention. Please plan on resending this series next week.
Please try to sort out the message threading - sending these as
separate emails seems to have fooled AI review.
AI review might have found several issues in here, all of them
pre-existing.
https://sashiko.dev/#/patchset/1F4441B54A305CC2+20260616055401.1570629-2-chenyichong@uniontech.com
https://sashiko.dev/#/patchset/B8742494160D4CAA+20260616055401.1570629-3-chenyichong@uniontech.com
Ye Liu and Zhen Ni (both cc'ed) have been working on page_owner
recently, so please let's keep them informed - they may be interested
in your changes and in the possible issues which Sashiko has
identified.
parent reply other threads:[~2026-06-25 4:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <16E1A77F98E4C49E+20260616055401.1570629-1-chenyichong@uniontech.com>]
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=20260624211544.8437baec5054d079e7ea30f0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chenyichong@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vishal.moola@gmail.com \
--cc=ye.liu@linux.dev \
--cc=zhen.ni@easystack.cn \
/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