From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,gehao@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-page_alloc-make-bad_range-return-bool.patch removed from -mm tree
Date: Fri, 23 Feb 2024 17:50:54 -0800 [thread overview]
Message-ID: <20240224015055.4BC77C43390@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/page_alloc: make bad_range() return bool
has been removed from the -mm tree. Its filename was
mm-page_alloc-make-bad_range-return-bool.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: Hao Ge <gehao@kylinos.cn>
Subject: mm/page_alloc: make bad_range() return bool
Date: Wed, 21 Feb 2024 15:32:27 +0800
bad_range() can return bool, so let us change it.
Link: https://lkml.kernel.org/r/20240221073227.276234-1-gehao@kylinos.cn
Signed-off-by: Hao Ge <gehao@kylinos.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_alloc.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--- a/mm/page_alloc.c~mm-page_alloc-make-bad_range-return-bool
+++ a/mm/page_alloc.c
@@ -464,19 +464,19 @@ static int page_outside_zone_boundaries(
/*
* Temporary debugging check for pages not lying within a given zone.
*/
-static int __maybe_unused bad_range(struct zone *zone, struct page *page)
+static bool __maybe_unused bad_range(struct zone *zone, struct page *page)
{
if (page_outside_zone_boundaries(zone, page))
- return 1;
+ return true;
if (zone != page_zone(page))
- return 1;
+ return true;
- return 0;
+ return false;
}
#else
-static inline int __maybe_unused bad_range(struct zone *zone, struct page *page)
+static inline bool __maybe_unused bad_range(struct zone *zone, struct page *page)
{
- return 0;
+ return false;
}
#endif
_
Patches currently in -mm which might be from gehao@kylinos.cn are
mm-page_alloc-make-check_new_page-return-bool.patch
reply other threads:[~2024-02-24 1:50 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=20240224015055.4BC77C43390@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=gehao@kylinos.cn \
--cc=mm-commits@vger.kernel.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 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.