[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YKecydxDtWLTDuKg@casper.infradead.org>
Date: Fri, 21 May 2021 12:43:05 +0100
From: Matthew Wilcox <willy@...radead.org>
To: "Uladzislau Rezki (Sony)" <urezki@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>,
Mel Gorman <mgorman@...e.de>,
Christoph Hellwig <hch@...radead.org>,
Nicholas Piggin <npiggin@...il.com>,
Hillf Danton <hdanton@...a.com>,
Michal Hocko <mhocko@...e.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@...ymobile.com>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] mm/vmalloc: Fallback to a single page allocator
On Fri, May 21, 2021 at 01:10:33PM +0200, Uladzislau Rezki (Sony) wrote:
> +static inline unsigned int
> +vm_area_alloc_pages(gfp_t gfp, int nid, unsigned int page_order,
> + unsigned long nr_small_pages, struct page **pages)
(at least) two tabs here, please, otherwise the argument list is at
the same indentation as the code which trips up my parser. some people
like to match the opening bracket, but that always feels like more work
than it's worth. fwiw, i'd format it like this:
static inline unsigned int vm_area_alloc_pages(gfp_t gfp, int nid,
unsigned int order, unsigned long nr_pages, struct page **pages)
{
...
(yes, i renamed some of the variables there; overly long variable names
are painful)
The rest of the patch looks good.
Reviewed-by: Matthew Wilcox (Oracle) <willy@...radead.org>
Powered by blists - more mailing lists