Re: [PATCH 1/2] mm/folio_queue: Delete __folio_order and use folio_order directly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Liu Ye <liuye@xxxxxxxxxx>
Subject: Re: [PATCH 1/2] mm/folio_queue: Delete __folio_order and use folio_order directly
From: David Howells <dhowells@xxxxxxxxxx>
Date: Wed, 12 Feb 2025 11:28:14 +0000
Cc: dhowells@xxxxxxxxxx, brauner@xxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
In-reply-to: <20250212025843.80283-2-liuye@kylinos.cn>
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903
References: <20250212025843.80283-2-liuye@kylinos.cn> <20250212025843.80283-1-liuye@kylinos.cn>

Liu Ye <liuye@xxxxxxxxxx> wrote:

> __folio_order is the same as folio_order, remove __folio_order and then
> just include mm.h and use folio_order directly.
> 
> Signed-off-by: Liu Ye <liuye@xxxxxxxxxx>

Acked-by: David Howells <dhowells@xxxxxxxxxx>

References:
- [PATCH 1/2] mm/folio_queue: Delete __folio_order and use folio_order directly
  - From: Liu Ye
- [PATCH 0/2] mm: Optimize folio_order.
  - From: Liu Ye

Prev by Date: Re: [RFC PATCH v5 0/7] mseal system mappings
Next by Date: [PATCH v5 15/18] zram: permit reclaim in zstd custom allocator
Previous by thread: Re: [PATCH 2/2] mm/mm.h: Write folio->_flags_1 & 0xff as a macro definition
Next by thread: [PATCH] mm/oom_kill: revert watchdog reset in global OOM process
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux