[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <595c96f5adcccd7eab9dc95eb48618981af66d3c.camel@perches.com>
Date: Wed, 19 Sep 2018 20:02:05 -0700
From: Joe Perches <joe@...ches.com>
To: Christophe Leroy <christophe.leroy@....fr>,
Andy Whitcroft <apw@...onical.com>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: Checkpatch bad Warning (Re: [PATCH] powerpc/kgdb: add
kgdb_arch_set/remove_breakpoint())
On Tue, 2018-09-18 at 09:33 +0000, Christophe Leroy wrote:
> On the below patch, checkpatch reports
>
> WARNING: struct kgdb_arch should normally be const
> #127: FILE: arch/powerpc/kernel/kgdb.c:480:
> +struct kgdb_arch arch_kgdb_ops;
>
> But when I add 'const', I get compilation failure
So don't add const.
checkpatch is stupid. You are not.
_Always_ take checkpatch bleats with very
large grains of salt.
Perhaps send a patch to remove kgbd_arch
from scripts/const_structs.checkpatch as
it seems not ever to be const.
Powered by blists - more mailing lists