From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,ziy@nvidia.com,akpm@linux-foundation.org
Subject: + mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix.patch added to mm-new branch
Date: Thu, 08 May 2025 15:58:08 -0700 [thread overview]
Message-ID: <20250508225808.D9F50C4CEED@smtp.kernel.org> (raw)
The patch titled
Subject: mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix
has been added to the -mm mm-new branch. Its filename is
mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix.patch
This patch will later appear in the mm-new branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Note, mm-new is a provisional staging ground for work-in-progress
patches, and acceptance into mm-new is a notification for others take
notice and to finish up reviews. Please do not hesitate to respond to
review feedback and post updated versions to replace or incrementally
fixup patches in mm-new.
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Zi Yan <ziy@nvidia.com>
Subject: mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix
Date: Thu, 8 May 2025 15:42:18 -0400
address the type issue reported by kernel test robot
1. fixed test_pages_isolated() and __test_page_isolated_in_pageblock()
signature by using the new isol_flags_t type.
2. fixed test_pages_isolated() doc: flags -> isol_flags
Link: https://lkml.kernel.org/r/C4D87FA7-4B3D-440F-9E5F-B57561AB4FE8@nvidia.com
Signed-off-by: Zi Yan <ziy@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/page-isolation.h | 2 +-
mm/page_isolation.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
--- a/include/linux/page-isolation.h~mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix
+++ a/include/linux/page-isolation.h
@@ -45,5 +45,5 @@ int start_isolate_page_range(unsigned lo
void undo_isolate_page_range(unsigned long start_pfn, unsigned long end_pfn);
int test_pages_isolated(unsigned long start_pfn, unsigned long end_pfn,
- int isol_flags);
+ isol_flags_t isol_flags);
#endif
--- a/mm/page_isolation.c~mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix
+++ a/mm/page_isolation.c
@@ -546,7 +546,7 @@ void undo_isolate_page_range(unsigned lo
*/
static unsigned long
__test_page_isolated_in_pageblock(unsigned long pfn, unsigned long end_pfn,
- int flags)
+ isol_flags_t flags)
{
struct page *page;
@@ -585,7 +585,7 @@ __test_page_isolated_in_pageblock(unsign
*
* This tests if all in the specified range are free.
*
- * If %MEMORY_OFFLINE is specified in @flags, it will consider
+ * If %MEMORY_OFFLINE is specified in @isol_flags, it will consider
* poisoned and offlined pages free as well.
*
* Caller must ensure the requested range doesn't span zones.
@@ -593,7 +593,7 @@ __test_page_isolated_in_pageblock(unsign
* Returns 0 if true, -EBUSY if one or more pages are in use.
*/
int test_pages_isolated(unsigned long start_pfn, unsigned long end_pfn,
- int isol_flags)
+ isol_flags_t isol_flags)
{
unsigned long pfn, flags;
struct page *page;
_
Patches currently in -mm which might be from ziy@nvidia.com are
mm-page_isolation-make-page-isolation-a-standalone-bit.patch
mm-page_isolation-remove-migratetype-from-move_freepages_block_isolate.patch
mm-page_isolation-remove-migratetype-from-undo_isolate_page_range.patch
mm-page_isolation-remove-migratetype-parameter-from-more-functions.patch
mm-page_isolation-remove-migratetype-parameter-from-more-functions-fix.patch
reply other threads:[~2025-05-08 22:58 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=20250508225808.D9F50C4CEED@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--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.