[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <33402181-6C78-4380-A02A-A36EDEBE4F30@linux.dev>
Date: Tue, 13 Jun 2023 10:18:29 +0800
From: Muchun Song <muchun.song@...ux.dev>
To: Tarun Sahu <tsahu@...ux.ibm.com>
Cc: Linux Memory Management List <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Kravetz <mike.kravetz@...cle.com>,
"Aneesh Kumar K . V" <aneesh.kumar@...ux.ibm.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Sidhartha Kumar <sidhartha.kumar@...cle.com>,
Gerald Schaefer <gerald.schaefer@...ux.ibm.com>,
linux-kernel@...r.kernel.org, jaypatel@...ux.ibm.com
Subject: Re: [PATCH] [mm-unstable] mm/folio: Replace set_compound_order with
folio_set_order
> On Jun 12, 2023, at 17:35, Tarun Sahu <tsahu@...ux.ibm.com> wrote:
>
> The patch [1] removed the need for special handling of order = 0
> in folio_set_order. Now, folio_set_order and set_compound_order becomes
> similar function. This patch removes the set_compound_order and uses
> folio_set_order instead.
>
> [1] https://lore.kernel.org/all/20230609183032.13E08C433D2@smtp.kernel.org/
>
> Signed-off-by: Tarun Sahu <tsahu@...ux.ibm.com>
Reviewed-by: Muchun Song <songmuchun@...edance.com>
Thanks.
Powered by blists - more mailing lists