From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org, rppt@kernel.org,
akpm@linux-foundation.org
Subject: [merged mm-stable] mm-move-free_area_empty-to-mm-internalh.patch removed from -mm tree
Date: Tue, 18 Apr 2023 16:33:50 -0700 [thread overview]
Message-ID: <20230418233350.E850DC433EF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: move free_area_empty() to mm/internal.h
has been removed from the -mm tree. Its filename was
mm-move-free_area_empty-to-mm-internalh.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: "Mike Rapoport (IBM)" <rppt@kernel.org>
Subject: mm: move free_area_empty() to mm/internal.h
Date: Sun, 26 Mar 2023 19:02:15 +0300
The free_area_empty() helper is only used inside mm/ so move it there to
reduce noise in include/linux/mmzone.h
Link: https://lkml.kernel.org/r/20230326160215.2674531-1-rppt@kernel.org
Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
Suggested-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/mmzone.h | 5 -----
mm/internal.h | 5 +++++
2 files changed, 5 insertions(+), 5 deletions(-)
--- a/include/linux/mmzone.h~mm-move-free_area_empty-to-mm-internalh
+++ a/include/linux/mmzone.h
@@ -110,11 +110,6 @@ struct free_area {
unsigned long nr_free;
};
-static inline bool free_area_empty(struct free_area *area, int migratetype)
-{
- return list_empty(&area->free_list[migratetype]);
-}
-
struct pglist_data;
#ifdef CONFIG_NUMA
--- a/mm/internal.h~mm-move-free_area_empty-to-mm-internalh
+++ a/mm/internal.h
@@ -517,6 +517,11 @@ void init_cma_reserved_pageblock(struct
int find_suitable_fallback(struct free_area *area, unsigned int order,
int migratetype, bool only_stealable, bool *can_steal);
+static inline bool free_area_empty(struct free_area *area, int migratetype)
+{
+ return list_empty(&area->free_list[migratetype]);
+}
+
/*
* These three helpers classifies VMAs for virtual memory accounting.
*/
_
Patches currently in -mm which might be from rppt@kernel.org are
reply other threads:[~2023-04-18 23:34 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=20230418233350.E850DC433EF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.org \
--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 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.