[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220126113339.GZ1951@kadam>
Date: Wed, 26 Jan 2022 14:33:39 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Colin Ian King <colin.i.king@...il.com>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H . Peter Anvin" <hpa@...or.com>,
linux-perf-users@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] perf/x86/rapl: replace 0 with NULL to initialize
pointers
On Tue, Jan 25, 2022 at 10:32:31PM +0100, Peter Zijlstra wrote:
> On Tue, Jan 25, 2022 at 08:14:03PM +0000, Colin Ian King wrote:
> > Pointers should be initialized with NULL rather than zero. Fix these.
>
> Why ? This isn't C++, heck, this isn't even C, this is the kernel, we
> hard rely on NULL being 0.
It's a Sparse warning.
https://www.spinics.net/lists/linux-sparse/msg10066.html
regards,
dan carpenter
Powered by blists - more mailing lists