From: Andrew Morton <akpm@linux-foundation.org>
To: Ye Liu <ye.liu@linux.dev>
Cc: Ye Liu <liuye@kylinos.cn>, David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] tools/mm/page_owner_sort: fix --sort, add module filter, improve usage
Date: Tue, 18 Aug 2026 20:17:04 -0700 [thread overview]
Message-ID: <20260818201704.26f48cb26420ad8ec00fd226@linux-foundation.org> (raw)
In-Reply-To: <20260819021611.2910835-1-ye.liu@linux.dev>
On Wed, 19 Aug 2026 10:16:08 +0800 Ye Liu <ye.liu@linux.dev> wrote:
> This series improves the page_owner_sort tool with a bug fix, a new
> module-name feature, and better usage text.
Cool, thanks. I remain mystified about the recent flurry of work on
page_owner. But I'm glad that people are obviously finding it useful!
I'll stash your series away for consideration after 7.3-rc1.
Sashiko claims to have found something rather obscure, but it's
probably worth cleaning that up:
https://sashiko.dev/#/patchset/20260819021611.2910835-1-ye.liu@linux.dev
prev parent reply other threads:[~2026-08-19 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 2:16 [PATCH v3 0/3] tools/mm/page_owner_sort: fix --sort, add module filter, improve usage Ye Liu
2026-08-19 2:16 ` [PATCH v3 1/3] tools/mm/page_owner_sort: fix --sort option being silently ignored Ye Liu
2026-08-19 2:16 ` [PATCH v3 2/3] tools/mm/page_owner_sort: add module name sort/cull/filter support Ye Liu
2026-08-19 2:16 ` [PATCH v3 3/3] tools/mm/page_owner_sort: show available sort keys in usage text Ye Liu
2026-08-19 3:17 ` 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=20260818201704.26f48cb26420ad8ec00fd226@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ye.liu@linux.dev \
/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.