Re: [PATCH 01/30] mm: move vma_start_pgoff() into mm.h and clean up
Gregory Price <[email protected]> Mon, 29 Jun 2026 11:27:26 -0400
| Newsgroups | org.kernel.vger.linux-sgx,dev.linux.lists.damon,dev.linux.lists.iommu,dev.linux.lists.nvdimm,org.freedesktop.lists.dri-devel,org.kernel.vger.kvm,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-parisc,org.kernel.vger.linux-perf-users,org.kernel.vger.linux-tegra,org.kernel.vger.linux-trace-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <akKO3vnNmWIJAZ7z@gourry-fedora-PF4VCD3F> |
On Mon, Jun 29, 2026 at 01:23:12PM +0100, Lorenzo Stoakes wrote: > vma_last_pgoff() already lives there, so it's a bit odd to keep > vma_start_pgoff() in mm/interval_tree.c. Move them together. > > These each return unsigned long, which pgoff_t is typedef'd to. Make this > consistent and have these functions return pgoff_t instead. > > Additionally, express vma_last_pgoff() in terms of vma_start_pgoff(), since > we wrap the vma->vm_pgoff access, we may as well use it here. > > Also while we're here, const-ify the VMA and cleanup a bit. > > No functional change intended. > > Signed-off-by: Lorenzo Stoakes <[email protected]> Reviewed-by: Gregory Price <[email protected]>