From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Marco Elver <elver@google.com>,
Jani Nikula <jani.nikula@intel.com>,
David Sterba <dsterba@suse.com>, Alex Shi <alexs@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
llvm@lists.linux.dev,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] treewide: use -Wdeclaration-after-statement
Date: Tue, 1 Mar 2022 12:20:10 -0800 [thread overview]
Message-ID: <CAHk-=wh4OdQANe7TLYGdPWUub0MEdbGDr72wpATHxypaSEGAyg@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdn-PrCUPe2WzLv18AH3=9DjtFES+r=M1DhoQivy8sHm-g@mail.gmail.com>
On Tue, Mar 1, 2022 at 12:06 PM Nick Desaulniers
<ndesaulniers@google.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.
Linus
next prev parent reply other threads:[~2022-03-01 20:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 14:52 [PATCH 1/3] [v3] Kbuild: move to -std=gnu11 Arnd Bergmann
2022-03-01 14:52 ` [PATCH 2/3] treewide: use -Wdeclaration-after-statement Arnd Bergmann
2022-03-01 16:54 ` Nathan Chancellor
2022-03-01 19:57 ` Nick Desaulniers
2022-03-01 20:06 ` Nick Desaulniers
2022-03-01 20:20 ` Linus Torvalds [this message]
2022-03-01 20:28 ` Nick Desaulniers
2022-03-03 0:44 ` Masahiro Yamada
2022-03-04 11:29 ` Sedat Dilek
2022-03-06 10:03 ` Sedat Dilek
2022-03-01 14:52 ` [PATCH 3/3] Kbuild: use -std=gnu11 for KBUILD_USERCFLAGS Arnd Bergmann
2022-03-01 17:00 ` Nathan Chancellor
2022-03-01 19:56 ` Nick Desaulniers
2022-03-02 22:14 ` Sedat Dilek
2022-03-02 22:54 ` Nick Desaulniers
2022-03-03 6:26 ` Sedat Dilek
2022-03-03 17:37 ` Nathan Chancellor
2022-03-04 6:47 ` Sedat Dilek
2022-03-04 7:18 ` Sedat Dilek
2022-03-04 11:12 ` Sedat Dilek
2022-03-06 10:04 ` Sedat Dilek
2022-03-01 16:53 ` [PATCH 1/3] [v3] Kbuild: move to -std=gnu11 Nathan Chancellor
2022-03-04 5:03 ` Masahiro Yamada
2022-03-04 11:24 ` Sedat Dilek
2022-03-06 10:01 ` Sedat Dilek
2022-03-04 11:37 ` Sedat Dilek
2022-03-04 16:25 ` Sedat Dilek
2022-03-06 15:31 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHk-=wh4OdQANe7TLYGdPWUub0MEdbGDr72wpATHxypaSEGAyg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dsterba@suse.com \
--cc=elver@google.com \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).