linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v1] mm: convert folio_page() back to a macro
Date: Thu, 25 Sep 2025 01:01:59 +0000	[thread overview]
Message-ID: <20250925010159.psdey3tir2wvlnoi@master> (raw)
In-Reply-To: <20250923140058.2020023-1-david@redhat.com>

On Tue, Sep 23, 2025 at 04:00:58PM +0200, David Hildenbrand wrote:
>In commit 73b3294b1152 ("mm: simplify folio_page() and folio_page_idx()")
>we converted folio_page() into a static inline function. However
>briefly afterwards in commit a847b17009ec ("mm: constify highmem related
>functions for improved const-correctness") we had to add some nasty
>const-away casting to make the compiler happy when checking const
>correctness.
>
>So let's just convert it back to a simple macro so the compiler can
>check const correctness properly. There is the alternative of
>using a _Generic() similar to page_folio(), but there is not a lot of
>benefit compared to just using a simple macro.
>
>Cc: Andrew Morton <akpm@linux-foundation.org>
>Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>
>Cc: Vlastimil Babka <vbabka@suse.cz>
>Cc: Mike Rapoport <rppt@kernel.org>
>Cc: Suren Baghdasaryan <surenb@google.com>
>Cc: Michal Hocko <mhocko@suse.com>
>Signed-off-by: David Hildenbrand <david@redhat.com>

Reviewed-by: Wei Yang <richard.weiyang@gmail.com>

-- 
Wei Yang
Help you, Help me


      parent reply	other threads:[~2025-09-25  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 14:00 David Hildenbrand
2025-09-23 15:31 ` Kiryl Shutsemau
2025-09-24  3:11 ` Lance Yang
2025-09-24  8:17 ` SeongJae Park
2025-09-24  8:57 ` Dev Jain
2025-09-24 16:45   ` Suren Baghdasaryan
2025-09-24 18:48 ` Vishal Moola (Oracle)
2025-09-25  1:01 ` Wei Yang [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=20250925010159.psdey3tir2wvlnoi@master \
    --to=richard.weiyang@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    /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