[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1yopRPex3yrKj50cRPy8d3+urGE2XN3aQ61Uu=FE8oVQ@mail.gmail.com>
Date: Wed, 21 Jun 2017 19:59:42 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Doug Anderson <dianders@...omium.org>,
Michal Marek <mmarek@...e.com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Grant Grundler <grundler@...omium.org>,
Greg Hackmann <ghackmann@...gle.com>,
Michael Davidson <md@...gle.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Bernhard Rosenkränzer <bero@...aro.org>
Subject: Re: [PATCH 2/2] kbuild: clang: Disable the 'duplicate-decl-specifier' warning
On Wed, Jun 21, 2017 at 6:58 PM, Matthias Kaehlcke <mka@...omium.org> wrote:
> El Wed, Jun 21, 2017 at 12:11:55PM +0200 Arnd Bergmann ha dit:
>> I see that container_of() has been modified in linux-next and no longer adds
>> the 'const' keyword, do we actually still need the patch?
>
> There is still (at least) the case of const arrays passed to
> MODULE_DEVICE_TABLE.
Does the 'const' have any effect there? As it's just an alias, it
should at least
not impact the placement of the symbol in the object file, right? Maybe we can
just remove that 'const' too. Do you see any other instances?
Arnd
Powered by blists - more mailing lists