From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,ying.huang@linux.alibaba.com,willy@infradead.org,rakie.kim@sk.com,matthew.brost@intel.com,joshua.hahnjy@gmail.com,gourry@gourry.net,david@kernel.org,byungchul@sk.com,apopple@nvidia.com,ziy@nvidia.com,akpm@linux-foundation.org
Subject: [folded-merged] migrate-optimise-alloc_migration_target-fix.patch removed from -mm tree
Date: Thu, 20 Nov 2025 13:29:29 -0800 [thread overview]
Message-ID: <20251120212929.DE596C4CEF1@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/migrate: fix zidx type
has been removed from the -mm tree. Its filename was
migrate-optimise-alloc_migration_target-fix.patch
This patch was dropped because it was folded into migrate-optimise-alloc_migration_target.patch
------------------------------------------------------
From: Zi Yan <ziy@nvidia.com>
Subject: mm/migrate: fix zidx type
Date: Thu, 6 Nov 2025 19:41:13 -0500
folio_zonenum() returns enum zone_type. It would be better to also
fix zidx's type.
Link: https://lkml.kernel.org/r/26E8FF35-503E-4F14-98F7-7B4FA25FBD37@nvidia.com
Signed-off-by: Zi Yan <ziy@nvidia.com>
Cc: Alistair Popple <apopple@nvidia.com>
Cc: Byungchul Park <byungchul@sk.com>
Cc: David Hildenbrand <david@kernel.org>
Cc: Gregory Price <gourry@gourry.net>
Cc: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Rakie Kim <rakie.kim@sk.com>
Cc: Ying Huang <ying.huang@linux.alibaba.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/migrate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/migrate.c~migrate-optimise-alloc_migration_target-fix
+++ a/mm/migrate.c
@@ -2165,7 +2165,7 @@ struct folio *alloc_migration_target(str
gfp_t gfp_mask;
unsigned int order = 0;
int nid;
- int zidx;
+ enum zone_type zidx;
mtc = (struct migration_target_control *)private;
gfp_mask = mtc->gfp_mask;
_
Patches currently in -mm which might be from ziy@nvidia.com are
migrate-optimise-alloc_migration_target.patch
mm-huge_memory-add-split_huge_page_to_order.patch
mm-memory-failure-improve-large-block-size-folio-handling.patch
mm-huge_memory-fix-kernel-doc-comments-for-folio_split-and-related.patch
mm-huge_memory-fix-kernel-doc-comments-for-folio_split-and-related-fix.patch
mm-huge_memory-fix-kernel-doc-comments-for-folio_split-and-related-fix-2.patch
reply other threads:[~2025-11-20 21:29 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=20251120212929.DE596C4CEF1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=matthew.brost@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=rakie.kim@sk.com \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.com \
/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.