[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aHddYU8elWhddpoP@localhost.localdomain>
Date: Wed, 16 Jul 2025 10:05:53 +0200
From: Oscar Salvador <osalvador@...e.de>
To: Anthony Yznaga <anthony.yznaga@...cle.com>
Cc: davem@...emloft.net, andreas@...sler.com, arnd@...db.de,
muchun.song@...ux.dev, akpm@...ux-foundation.org, david@...hat.com,
lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, vbabka@...e.cz,
rppt@...nel.org, surenb@...gle.com, mhocko@...e.com,
linux-mm@...ck.org, sparclinux@...r.kernel.org,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
alexghiti@...osinc.com, agordeev@...ux.ibm.com,
anshuman.khandual@....com, christophe.leroy@...roup.eu,
ryan.roberts@....com, will@...nel.org
Subject: Re: [PATCH 0/3] drop hugetlb_free_pgd_range()
On Tue, Jul 15, 2025 at 06:26:08PM -0700, Anthony Yznaga wrote:
> For all architectures that support hugetlb except for sparc,
> hugetlb_free_pgd_range() just calls free_pgd_range(). It turns out
> the sparc implementation is essentially identical to free_pgd_range()
> and can be removed. Remove it and update free_pgtables() to treat
> hugetlb VMAs the same as others.
>
> Anthony Yznaga (3):
> sparc64: remove hugetlb_free_pgd_range()
> mm: remove call to hugetlb_free_pgd_range()
> mm: drop hugetlb_free_pgd_range()
Acked-by: Oscar Salvador <osalvador@...e.de>
Thanks!
--
Oscar Salvador
SUSE Labs
Powered by blists - more mailing lists