From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,youling.tang@linux.dev,tangyouling@kylinos.cn,max.kellermann@ionos.com,chizhiling@kylinos.cn,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] mm-filemap-align-last_index-to-folio-size-fix-fix.patch removed from -mm tree
Date: Sun, 21 Sep 2025 13:06:28 -0700 [thread overview]
Message-ID: <20250921200628.C43ADC4CEE7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-filemap-align-last_index-to-folio-size-fix-fix
has been removed from the -mm tree. Its filename was
mm-filemap-align-last_index-to-folio-size-fix-fix.patch
This patch was dropped because it was folded into mm-filemap-align-last_index-to-folio-size.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-filemap-align-last_index-to-folio-size-fix-fix
Date: Wed Sep 3 03:50:51 PM PDT 2025
update it for Max's constification efforts
Cc: Max Kellermann <max.kellermann@ionos.com>
Cc: Chi Zhiling <chizhiling@kylinos.cn>
Cc: Youling Tang <tangyouling@kylinos.cn>
Cc: Youling Tang <youling.tang@linux.dev>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/pagemap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/include/linux/pagemap.h~mm-filemap-align-last_index-to-folio-size-fix-fix
+++ a/include/linux/pagemap.h
@@ -483,7 +483,7 @@ mapping_min_folio_nrpages(const struct a
}
static inline unsigned long
-mapping_min_folio_nrbytes(struct address_space *mapping)
+mapping_min_folio_nrbytes(const struct address_space *mapping)
{
return mapping_min_folio_nrpages(mapping) << PAGE_SHIFT;
}
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
kasan-fix-warnings-caused-by-use-of-arch_enter_lazy_mmu_mode-fix.patch
mm-filemap-align-last_index-to-folio-size.patch
mm-re-enable-kswapd-when-memory-pressure-subsides-or-demotion-is-toggled-fix.patch
include-linux-pgtableh-convert-arch_enter_lazy_mmu_mode-and-friends-to-static-inlines.patch
alloc_tag-mark-inaccurate-allocation-counters-in-proc-allocinfo-output-fix-fix.patch
alloc_tag-mark-inaccurate-allocation-counters-in-proc-allocinfo-output-fix-fix-fix.patch
mm-add-remap_pfn_range_prepare-remap_pfn_range_complete-fix.patch
mm-vmalloc-move-resched-point-into-alloc_vmap_area-fix.patch
mm-vmscan-remove-folio_test_private-check-in-pageout-fix.patch
kho-add-support-for-preserving-vmalloc-allocations-checkpatch-fixes.patch
reply other threads:[~2025-09-21 20:06 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=20250921200628.C43ADC4CEE7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=chizhiling@kylinos.cn \
--cc=max.kellermann@ionos.com \
--cc=mm-commits@vger.kernel.org \
--cc=tangyouling@kylinos.cn \
--cc=youling.tang@linux.dev \
/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.