[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220510101600.48529d5e@gandalf.local.home>
Date: Tue, 10 May 2022 10:16:00 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Vasily Averin <vvs@...nvz.org>
Cc: kernel test robot <lkp@...el.com>, Ingo Molnar <mingo@...hat.com>,
kbuild-all@...ts.01.org, Shakeel Butt <shakeelb@...gle.com>,
kernel@...nvz.org, linux-kernel@...r.kernel.org,
Roman Gushchin <roman.gushchin@...ux.dev>,
Vlastimil Babka <vbabka@...e.cz>,
Michal Hocko <mhocko@...e.com>, cgroups@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Dennis Zhou <dennis@...nel.org>, Tejun Heo <tj@...nel.org>,
Christoph Lameter <cl@...ux-foundation.org>
Subject: Re: [PATCH] percpu: improve percpu_alloc_percpu event trace
On Tue, 10 May 2022 07:22:02 +0300
Vasily Averin <vvs@...nvz.org> wrote:
> ... and when __def_gfpflag_names() traslates them to unsigned long
>
> {(unsigned long)GFP_DMA, "GFP_DMA"}, \
> {(unsigned long)__GFP_HIGHMEM, "__GFP_HIGHMEM"}, \
> {(unsigned long)GFP_DMA32, "GFP_DMA32"}, \
>
> ... it leads to sparse warnings bacuse type gfp_t was declared as 'bitwise'
Ah' it's the printing of the flag bits. Got it.
-- Steve
Powered by blists - more mailing lists