From: Christoph Hellwig <hch@lst.de>
To: Alistair Popple <apopple@nvidia.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
gerald.schaefer@linux.ibm.com, dan.j.williams@intel.com,
jgg@ziepe.ca, willy@infradead.org, david@redhat.com,
linux-kernel@vger.kernel.org, nvdimm@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, jhubbard@nvidia.com, hch@lst.de
Subject: Re: [RFC 3/4] mm: Remove callers of pfn_t functionality
Date: Wed, 8 Jan 2025 06:53:09 +0100 [thread overview]
Message-ID: <20250108055309.GD20341@lst.de> (raw)
In-Reply-To: <b5b3b567ce2d1df7186ad79bcda7cec6e82f2a1f.1736299058.git-series.apopple@nvidia.com>
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@lst.de>
Would be nice if you'd fix up the created overly long line everywhere
and not just in a few places, though.
next prev parent reply other threads:[~2025-01-08 5:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 1:18 [RFC 0/4] mm: Remove pfn_t type Alistair Popple
2025-01-08 1:18 ` [RFC 1/4] mm: Remove PFN_MAP, PFN_SG_CHAIN and PFN_SG_LAST Alistair Popple
2025-01-08 5:51 ` Christoph Hellwig
2025-01-08 1:18 ` [RFC 2/4] mm: Remove uses of PFN_DEV Alistair Popple
2025-01-08 5:51 ` Christoph Hellwig
2025-01-08 1:18 ` [RFC 3/4] mm: Remove callers of pfn_t functionality Alistair Popple
2025-01-08 5:53 ` Christoph Hellwig [this message]
2025-01-08 1:18 ` [RFC 4/4] mm: Remove include/linux/pfn_t.h Alistair Popple
2025-01-08 5:53 ` Christoph Hellwig
2025-01-08 19:36 ` [RFC 0/4] mm: Remove pfn_t type Dan Williams
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=20250108055309.GD20341@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.