[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZRIQjZOZJ2ZFkY8C@casper.infradead.org>
Date: Mon, 25 Sep 2023 23:58:21 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Hugh Dickins <hughd@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <ak@...ux.intel.com>,
Christoph Lameter <cl@...ux.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
David Hildenbrand <david@...hat.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Yang Shi <shy828301@...il.com>,
Sidhartha Kumar <sidhartha.kumar@...cle.com>,
Vishal Moola <vishal.moola@...il.com>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Tejun Heo <tj@...nel.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Michal Hocko <mhocko@...e.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH 09/12] mm: add page_rmappable_folio() wrapper
On Mon, Sep 25, 2023 at 01:32:02AM -0700, Hugh Dickins wrote:
> {
> struct page *page = __alloc_pages(gfp | __GFP_COMP, order,
> - preferred_nid, nodemask);
> + preferred_nid, nodemask);
I really prefer not to do this "align arguments with opening bracket"
style. As long as they're indented enough to make them visually distinct
from indentation-for-if-blocks, I find it annoying when functions get
renamed to something with a different length and somebody then wastes
time reindenting all the arguments to match.
> + return page_rmappable_folio(page);
I don't particularly object to the main thrust of this patch. I'm not
sure I like it in huge_mm.h though. Maybe in mm/internal.h? I
wouldn't want anyone outside mm/ calling it.
Powered by blists - more mailing lists