From: Andrew Morton <akpm@linux-foundation.org>
To: Ye Liu <ye.liu@linux.dev>
Cc: Zi Yan <ziy@nvidia.com>, Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/9] mm/page_owner: misc cleanups
Date: Fri, 10 Jul 2026 14:27:32 -0700 [thread overview]
Message-ID: <20260710142732.e4b0a719d5247e693f7a89a1@linux-foundation.org> (raw)
In-Reply-To: <9d8627fe-1fb6-47ff-9ca9-ff3b90a12bd8@linux.dev>
On Fri, 10 Jul 2026 15:05:18 +0800 Ye Liu <ye.liu@linux.dev> wrote:
> Sorry Andrew, I had more time last week and updated more frequently.
> I will wait and communicate fully for each version.
>
> > btw, it's conventional to place the what-changed-since-last-time info
> > below the ^---$ separator rather than at top-of-changelog. That's where
> > we place info which isn't appropriate for the mainline tree.
> >
> I also have a question about this. Is the changelog placed in [PATCH 0/N]
> or in the patch [PATCH M/N] that needs to be modified?
> I've looked at some content on the mailing list,
> and it seems there are both options.
Please do it this way in the [0/N] and in the individual patches.
Anything which isn't to be kept in the permanent upstream record should
be placed below the --- separator, please. Low-level development-time
details aren't of interest to readers two years from now.
prev parent reply other threads:[~2026-07-10 21:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 6:10 [PATCH v5 0/9] mm/page_owner: misc cleanups Ye Liu
2026-07-01 6:10 ` [PATCH v5 1/9] mm/page_owner: extract skip_buddy_pages() helper to unify buddy page skipping Ye Liu
2026-07-01 6:10 ` [PATCH v5 2/9] mm/page_owner: add MR_NEVER to enum migrate_reason and use it for last_migrate_reason Ye Liu
2026-07-01 6:10 ` [PATCH v5 3/9] mm: use enum migrate_reason instead of int for migration reason parameters Ye Liu
2026-07-01 10:23 ` Lorenzo Stoakes
2026-07-06 18:34 ` David Hildenbrand (Arm)
2026-07-01 6:10 ` [PATCH v5 4/9] mm/page_owner: hoist CONFIG_MEMCG to function level for print_page_owner_memcg() Ye Liu
2026-07-01 6:10 ` [PATCH v5 5/9] mm/page_owner: add missing newline to count_threshold format string Ye Liu
2026-07-01 6:10 ` [PATCH v5 6/9] mm/page_owner: move free_ts_nsec output to free section in __dump_page_owner() Ye Liu
2026-07-01 6:10 ` [PATCH v5 7/9] mm/page_owner: drop redundant page_owner prefix from static symbols Ye Liu
2026-07-01 6:10 ` [PATCH v5 8/9] mm/page_owner: clamp skip_buddy_pages() PFN advance at MAX_ORDER_NR_PAGES boundary Ye Liu
2026-07-01 6:34 ` Vlastimil Babka (SUSE)
2026-07-02 2:44 ` Zi Yan
2026-07-01 6:10 ` [PATCH v5 9/9] mm/page_owner: use memcg_data snapshot instead of PageMemcgKmem() to avoid TOCTOU VM_BUG_ON Ye Liu
2026-07-01 6:49 ` Vlastimil Babka (SUSE)
2026-07-02 2:02 ` Zi Yan
2026-07-10 6:51 ` Ye Liu
2026-07-10 15:56 ` Zi Yan
2026-07-02 0:11 ` [PATCH v5 0/9] mm/page_owner: misc cleanups Andrew Morton
2026-07-10 7:05 ` Ye Liu
2026-07-10 21:27 ` 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=20260710142732.e4b0a719d5247e693f7a89a1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ye.liu@linux.dev \
--cc=ziy@nvidia.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