[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZuMk2Yc7i-JMiHpA@casper.infradead.org>
Date: Thu, 12 Sep 2024 18:28:57 +0100
From: Matthew Wilcox <willy@...radead.org>
To: "Christoph Lameter (Ampere)" <cl@...two.org>
Cc: kernel test robot <lkp@...el.com>,
Christoph Lameter via B4 Relay <devnull+cl.gentwo.org@...nel.org>,
Vlastimil Babka <vbabka@...e.cz>, Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Hyeonggon Yoo <42.hyeyoo@...il.com>, Yang Shi <shy828301@...il.com>,
oe-kbuild-all@...ts.linux.dev,
Linux Memory Management List <linux-mm@...ck.org>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Huang Shijie <shijie@...amperecomputing.com>
Subject: Re: [PATCH v2] SLUB: Add support for per object memory policies
On Thu, Sep 12, 2024 at 09:15:34AM -0700, Christoph Lameter (Ampere) wrote:
> > sparse warnings: (new ones prefixed by >>)
> > >> mm/slub.c:222:1: sparse: sparse: symbol 'strict_numa' was not declared. Should it be static?
>
>
> Ummm.. This code declares strict_numa. Whats wrong with sparc64 / sparse ?
>
> > vim +/strict_numa +222 mm/slub.c
> >
> > 220
> > 221 #ifdef CONFIG_NUMA
> > > 222 DEFINE_STATIC_KEY_FALSE(strict_numa);
maybe this should be:
static DEFINE_STATIC_KEY_FALSE(strict_numa);
if it's only used within mm/slub.c? Or it needs to be declared in a
header file if it is used outside mm/slub.c.
> > 223 #endif
> > 224
> >
>
>
Powered by blists - more mailing lists