From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, cuigaosheng1@huawei.com,
akpm@linux-foundation.org
Subject: [merged mm-stable] mm-remove-unused-inline-functions-from-include-linux-mm_inlineh.patch removed from -mm tree
Date: Mon, 03 Oct 2022 14:10:13 -0700 [thread overview]
Message-ID: <20221003211014.5714BC433D6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: remove unused inline functions from include/linux/mm_inline.h
has been removed from the -mm tree. Its filename was
mm-remove-unused-inline-functions-from-include-linux-mm_inlineh.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: Gaosheng Cui <cuigaosheng1@huawei.com>
Subject: mm: remove unused inline functions from include/linux/mm_inline.h
Date: Thu, 22 Sep 2022 19:09:35 +0800
Remove the following unused inline functions from mm_inline.h:
1. All uses of add_page_to_lru_list_tail() have been removed since
commit 7a3dbfe8a52b ("mm/swap: convert lru_deactivate_file to a
folio_batch"), and it can be replaced by lruvec_add_folio_tail().
2. All uses of __clear_page_lru_flags() have been removed since commit
188e8caee968 ("mm/swap: convert __page_cache_release() to use a
folio"), and it can be replaced by __folio_clear_lru_flags().
They are useless, so remove them.
Link: https://lkml.kernel.org/r/20220922110935.1495099-1-cuigaosheng1@huawei.com
Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/mm_inline.h | 11 -----------
1 file changed, 11 deletions(-)
--- a/include/linux/mm_inline.h~mm-remove-unused-inline-functions-from-include-linux-mm_inlineh
+++ a/include/linux/mm_inline.h
@@ -76,11 +76,6 @@ static __always_inline void __folio_clea
__folio_clear_unevictable(folio);
}
-static __always_inline void __clear_page_lru_flags(struct page *page)
-{
- __folio_clear_lru_flags(page_folio(page));
-}
-
/**
* folio_lru_list - Which LRU list should a folio be on?
* @folio: The folio to test.
@@ -348,12 +343,6 @@ void lruvec_add_folio_tail(struct lruvec
list_add_tail(&folio->lru, &lruvec->lists[lru]);
}
-static __always_inline void add_page_to_lru_list_tail(struct page *page,
- struct lruvec *lruvec)
-{
- lruvec_add_folio_tail(lruvec, page_folio(page));
-}
-
static __always_inline
void lruvec_del_folio(struct lruvec *lruvec, struct folio *folio)
{
_
Patches currently in -mm which might be from cuigaosheng1@huawei.com are
reply other threads:[~2022-10-03 21:18 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=20221003211014.5714BC433D6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=cuigaosheng1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--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.