From: "David Hildenbrand (arm)" <david@kernel.org>
To: Jiaqi Yan <jiaqiyan@google.com>,
jane.chu@oracle.com, muchun.song@linux.dev
Cc: akpm@linux-foundation.org, osalvador@suse.de,
william.roche@oracle.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs: hugetlb: simplify remove_inode_hugepages() return type
Date: Wed, 4 Feb 2026 22:54:48 +0100 [thread overview]
Message-ID: <17af6fe6-9318-4e9c-ba54-0b6b16ea9c0c@kernel.org> (raw)
In-Reply-To: <20260204214741.3161520-1-jiaqiyan@google.com>
On 2/4/26 22:47, Jiaqi Yan wrote:
> When remove_inode_hugepages is introduced in
> commit c86272287bc6 ("hugetlb: create remove_inode_single_folio to remove single file folio")
> it used to return a boolean to indicate if it bailed out due to race with
> page faults. However, since the race is already solved by [1],
> remove_inode_hugepages() doesn't have any path to return false anymore.
>
> Simplify remove_inode_hugepages() return type to void, remove the
> unnecessary ret variable, and adjust the call site in
> remove_inode_hugepages(). No functional change in this commit.
>
> Changelog
> =========
>
> v2 -> v1 [2]
>
> - Use two-tab alignment for parameters wrapped to new lines.
>
> - Remove return type in remove_inode_hugepages()'s comment.
>
> [1] https://lore.kernel.org/all/20220914221810.95771-10-mike.kravetz@oracle.com
> [2] https://lore.kernel.org/linux-mm/20260202233617.2350734-1-jiaqiyan@google.com
>
> Suggested-by: Jane Chu <jane.chu@oracle.com>
> Reviewed-by: Jane Chu <jane.chu@oracle.com>
> Reviewed-by: Muchun Song <muchun.song@linux.dev>
> Acked-by: David Hildenbrand (arm) <david@kernel.org>
> Signed-off-by: Jiaqi Yan <jiaqiyan@google.com>
> ---
For the future, the changelog always belongs down here, under the ---, like
Signed-off-by: Jiaqi Yan <jiaqiyan@google.com>
---
Changelog
...
fs/hugetlbfs/inode.c | 18 ++++++------------
1 file changed, 6 insertions(+), 12 deletions(-)
I think I always add another "---" above the file list, not sure if that
is required.
I'm sure Andrew can fix that up when applying, thanks!
--
Cheers,
David
next prev parent reply other threads:[~2026-02-04 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 21:47 Jiaqi Yan
2026-02-04 21:54 ` David Hildenbrand (arm) [this message]
2026-02-04 22:44 ` Andrew Morton
2026-02-05 1:13 ` SeongJae Park
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=17af6fe6-9318-4e9c-ba54-0b6b16ea9c0c@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=william.roche@oracle.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