[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOd=TpqiSSh3yqQ2Z44nJArBACvfohVCgd6Ej32rGQMvShA@mail.gmail.com>
Date: Tue, 1 Mar 2022 12:28:38 -0800
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Arnd Bergmann <arnd@...nel.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Arnd Bergmann <arnd@...db.de>, Marco Elver <elver@...gle.com>,
Jani Nikula <jani.nikula@...el.com>,
David Sterba <dsterba@...e.com>, Alex Shi <alexs@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
llvm@...ts.linux.dev,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] treewide: use -Wdeclaration-after-statement
On Tue, Mar 1, 2022 at 12:20 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Tue, Mar 1, 2022 at 12:06 PM Nick Desaulniers
> <ndesaulniers@...gle.com> wrote:
> >
> > That said, there's a few additional places that reset KBUILD_CFLAGS.
>
> Yeah, the boot code and vdso code often sets its own private flags,
> because it's _so_ different.
>
> The generic kernel CFLAGS often don't work at all, because that code
> may be doing some truly horrendous things.
>
> So I agree that this may not catch all the kernel code, but I don't
> think it's much of a problem.
Agreed; they can still mirror the style imposed by
-Wdeclaration-after-statement like the rest of the codebase though.
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists