From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org,
usama.arif@bytedance.com, songmuchun@bytedance.com,
mike.kravetz@oracle.com, sidhartha.kumar@oracle.com,
akpm@linux-foundation.org
Subject: [merged mm-stable] mm-hugetlb-replace-page_ref_freeze-with-folio_ref_freeze-in-hugetlb_folio_init_vmemmap.patch removed from -mm tree
Date: Fri, 06 Oct 2023 14:48:28 -0700 [thread overview]
Message-ID: <20231006214830.D7ACAC433C7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/hugetlb: replace page_ref_freeze() with folio_ref_freeze() in hugetlb_folio_init_vmemmap()
has been removed from the -mm tree. Its filename was
mm-hugetlb-replace-page_ref_freeze-with-folio_ref_freeze-in-hugetlb_folio_init_vmemmap.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: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Subject: mm/hugetlb: replace page_ref_freeze() with folio_ref_freeze() in hugetlb_folio_init_vmemmap()
Date: Tue, 26 Sep 2023 10:44:33 -0700
No functional difference, folio_ref_freeze() is currently a wrapper for
page_ref_freeze().
Link: https://lkml.kernel.org/r/20230926174433.81241-1-sidhartha.kumar@oracle.com
Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Reviewed-by: Muchun Song <songmuchun@bytedance.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Usama Arif <usama.arif@bytedance.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/hugetlb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/hugetlb.c~mm-hugetlb-replace-page_ref_freeze-with-folio_ref_freeze-in-hugetlb_folio_init_vmemmap
+++ a/mm/hugetlb.c
@@ -3191,7 +3191,7 @@ static void __init hugetlb_folio_init_vm
/* Prepare folio head */
__folio_clear_reserved(folio);
__folio_set_head(folio);
- ret = page_ref_freeze(&folio->page, 1);
+ ret = folio_ref_freeze(folio, 1);
VM_BUG_ON(!ret);
/* Initialize the necessary tail struct pages */
hugetlb_folio_init_tail_vmemmap(folio, 1, nr_pages);
_
Patches currently in -mm which might be from sidhartha.kumar@oracle.com are
reply other threads:[~2023-10-06 21:48 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=20231006214830.D7ACAC433C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mm-commits@vger.kernel.org \
--cc=sidhartha.kumar@oracle.com \
--cc=songmuchun@bytedance.com \
--cc=usama.arif@bytedance.com \
--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.