From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,willy@infradead.org,jack@suse.cz,tanze@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-filemap-use-folio_next_index-for-start.patch removed from -mm tree
Date: Mon, 08 Jun 2026 18:22:51 -0700 [thread overview]
Message-ID: <20260609012251.ADE681F00899@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/filemap: use folio_next_index() for start
has been removed from the -mm tree. Its filename was
mm-filemap-use-folio_next_index-for-start.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: tanze <tanze@kylinos.cn>
Subject: mm/filemap: use folio_next_index() for start
Date: Mon, 1 Jun 2026 19:04:23 +0800
Use folio_next_index() instead of open-coding folio->index +
folio_nr_pages(folio) when updating @start in filemap_get_folios_contig(),
filemap_get_folios_tag(), and filemap_get_folios_dirty().
Link: https://lore.kernel.org/20260601110425.44784-1-tanze@kylinos.cn
Signed-off-by: tanze <tanze@kylinos.cn>
Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/filemap.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
--- a/mm/filemap.c~mm-filemap-use-folio_next_index-for-start
+++ a/mm/filemap.c
@@ -2284,8 +2284,7 @@ unsigned filemap_get_folios_contig(struc
goto put_folio;
if (!folio_batch_add(fbatch, folio)) {
- nr = folio_nr_pages(folio);
- *start = folio->index + nr;
+ *start = folio_next_index(folio);
goto out;
}
xas_advance(&xas, folio_next_index(folio) - 1);
@@ -2345,8 +2344,7 @@ unsigned filemap_get_folios_tag(struct a
if (xa_is_value(folio))
continue;
if (!folio_batch_add(fbatch, folio)) {
- unsigned long nr = folio_nr_pages(folio);
- *start = folio->index + nr;
+ *start = folio_next_index(folio);
goto out;
}
}
@@ -2404,8 +2402,7 @@ unsigned filemap_get_folios_dirty(struct
}
}
if (!folio_batch_add(fbatch, folio)) {
- unsigned long nr = folio_nr_pages(folio);
- *start = folio->index + nr;
+ *start = folio_next_index(folio);
goto out;
}
}
_
Patches currently in -mm which might be from tanze@kylinos.cn are
reply other threads:[~2026-06-09 1:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260609012251.ADE681F00899@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=tanze@kylinos.cn \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox