[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250108055309.GD20341@lst.de>
Date: Wed, 8 Jan 2025 06:53:09 +0100
From: Christoph Hellwig <hch@....de>
To: Alistair Popple <apopple@...dia.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org,
gerald.schaefer@...ux.ibm.com, dan.j.williams@...el.com,
jgg@...pe.ca, willy@...radead.org, david@...hat.com,
linux-kernel@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org, jhubbard@...dia.com, hch@....de
Subject: Re: [RFC 3/4] mm: Remove callers of pfn_t functionality
On Wed, Jan 08, 2025 at 12:18:47PM +1100, Alistair Popple wrote:
> All PFN_* pfn_t flags have been removed. Therefore there is no longer
> a need for the pfn_t type and all uses can be replaced with normal
> pfns.
Looks good in general:
Reviewed-by: Christoph Hellwig <hch@....de>
Would be nice if you'd fix up the created overly long line everywhere
and not just in a few places, though.
Powered by blists - more mailing lists