From: Zi Yan <ziy@nvidia.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: [PATCH 01/11] mm: Introduce memdesc_flags_t
Date: Wed, 06 Aug 2025 14:24:03 -0400 [thread overview]
Message-ID: <26FC57F0-BF7D-4F02-9736-F15B4B56466A@nvidia.com> (raw)
In-Reply-To: <20250805172307.1302730-2-willy@infradead.org>
On 5 Aug 2025, at 13:22, Matthew Wilcox (Oracle) wrote:
> Wrap the unsigned long flags in a typedef. In upcoming patches, this
> will provide a strong hint that you can't just pass a random unsigned
> long to functions which take this as an argument.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> ---
> arch/x86/mm/pat/memtype.c | 6 ++---
> fs/fuse/dev.c | 2 +-
> fs/gfs2/glops.c | 2 +-
> fs/jffs2/file.c | 4 ++--
> fs/nilfs2/page.c | 2 +-
> fs/proc/page.c | 4 ++--
> fs/ubifs/file.c | 6 ++---
> include/linux/mm.h | 32 +++++++++++++-------------
> include/linux/mm_inline.h | 12 +++++-----
> include/linux/mm_types.h | 8 +++++--
> include/linux/mmzone.h | 2 +-
> include/linux/page-flags.h | 40 ++++++++++++++++-----------------
> include/linux/pgalloc_tag.h | 7 +++---
> include/trace/events/page_ref.h | 4 ++--
> mm/filemap.c | 8 +++----
> mm/huge_memory.c | 4 ++--
> mm/memory-failure.c | 12 +++++-----
> mm/mmzone.c | 4 ++--
> mm/page_alloc.c | 12 +++++-----
> mm/swap.c | 8 +++----
> mm/vmscan.c | 18 +++++++--------
> mm/workingset.c | 2 +-
> 22 files changed, 102 insertions(+), 97 deletions(-)
LGTM. The change also compiles.
Acked-by: Zi Yan <ziy@nvidia.com>
--
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-08-06 18:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 17:22 [PATCH 00/11] Add and use memdesc_flags_t Matthew Wilcox (Oracle)
2025-08-05 17:22 ` [PATCH 01/11] mm: Introduce memdesc_flags_t Matthew Wilcox (Oracle)
2025-08-06 18:24 ` Zi Yan [this message]
2025-08-19 17:49 ` Kairui Song
2025-08-19 17:58 ` Matthew Wilcox
2025-08-19 18:03 ` Kairui Song
2025-08-05 17:22 ` [PATCH 02/11] mm: Convert page_to_section() to memdesc_section() Matthew Wilcox (Oracle)
2025-08-06 18:31 ` Zi Yan
2025-08-05 17:22 ` [PATCH 03/11] mm: Introduce memdesc_nid() Matthew Wilcox (Oracle)
2025-08-06 18:47 ` Zi Yan
2025-08-06 19:04 ` Matthew Wilcox
2025-08-06 19:07 ` Zi Yan
2025-08-05 17:22 ` [PATCH 04/11] mm: Introduce memdesc_zonenum() Matthew Wilcox (Oracle)
2025-08-06 18:57 ` Zi Yan
2025-08-05 17:22 ` [PATCH 05/11] slab: Use memdesc_flags_t Matthew Wilcox (Oracle)
2025-08-06 19:16 ` Zi Yan
2025-08-05 17:22 ` [PATCH 06/11] slab: Use memdesc_nid() Matthew Wilcox (Oracle)
2025-08-06 19:17 ` Zi Yan
2025-08-05 17:22 ` [PATCH 07/11] mm: Introduce memdesc_is_zone_device() Matthew Wilcox (Oracle)
2025-08-06 19:22 ` Zi Yan
2025-08-05 17:22 ` [PATCH 08/11] mm: Reimplement folio_is_device_private() Matthew Wilcox (Oracle)
2025-08-06 19:25 ` Zi Yan
2025-08-05 17:22 ` [PATCH 09/11] mm: Reimplement folio_is_device_coherent() Matthew Wilcox (Oracle)
2025-08-06 19:27 ` Zi Yan
2025-08-05 17:23 ` [PATCH 10/11] mm: Reimplement folio_is_fsdax() Matthew Wilcox (Oracle)
2025-08-06 19:27 ` Zi Yan
2025-08-05 17:23 ` [PATCH 11/11] mm: Add folio_is_pci_p2pdma() Matthew Wilcox (Oracle)
2025-08-05 21:40 ` [PATCH 00/11] Add and use memdesc_flags_t Shakeel Butt
2025-08-06 12:55 ` Matthew Wilcox
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=26FC57F0-BF7D-4F02-9736-F15B4B56466A@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/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 NNTP newsgroup(s).