mm-vmallocc-use-high-order-in-description-non-0-order-pages.patch removed from -mm tree
The quilt patch titled
Subject: mm/vmalloc.c: use "high-order" in description non 0-order pages
has been removed from the -mm tree. Its filename was
mm-vmallocc-use-high-order-in-description-non-0-order-pages.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: "Uladzislau Rezki (Sony)" <[email protected]>
Subject: mm/vmalloc.c: use "high-order" in description non 0-order pages
Date: Fri, 6 Sep 2024 11:50:49 +0200
In many places, in the comments, we use both "higher-order" and "high-order" to describe the non 0-order pages. That is confusing, because a "higher-order" statement does not reflect what it is compared with.
---
mm/vmalloc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
mm/vmalloc.c renamed from mm/vmalloc.c~mm-vmallocc-use-high-order-in-description-non-0-order-pages +2 -2
@@ -3570,7 +3570,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid,break ;/* -* Higher order allocations must be able to be treated as +* High-order allocations must be able to be treated as * independent small pages by callers (as they can with * small-page vmallocs). Some drivers do their own refcounting * on vmalloc_to_page() pages, some use page->mapping,
@@ -3633,7 +3633,7 @@ static void *__vmalloc_area_node(struct page_order =vm_area_page_order (area);/* -* Higher order nofail allocations are really expensive and +* High-order nofail allocations are really expensive and * potentially dangerous (pre-mature OOM, disruptive reclaim * and compaction etc. *
_
Patches currently in -mm which might be from [email protected] are