From: Arnd Bergmann <arnd@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
llvm@lists.linux.dev
Subject: [PATCH 0/4] Enable more warnings by default
Date: Thu, 4 Apr 2024 17:16:53 +0200 [thread overview]
Message-ID: <20240404151713.3493098-1-arnd@kernel.org> (raw)
From: Arnd Bergmann <arnd@arndb.de>
I think these can now get merged into linux-next. I reordered
these slightly from my previous submission to skip the
-Wcast-function-type-strict warnings but instead include the
-Wformat-truncation enablement, based on what got merged so
far.
We are still missing the "kallsyms: rework symbol lookup return codes"
and "firmware: dmi-id: add a release callback function" patches, but
I expect them to get merged through the respective trees soon.
There is still an open question about the order of patches in the
coming merge window: if some of the other patches are also queued
for 6.10 rather than 6.9, this series has to come after those to
avoid regressions. Maybe they can go into some kind of 'kbuild/late'
branch that gets merged in the second half of the merge window?
Arnd
Link: https://lore.kernel.org/lkml/20240326223825.4084412-1-arnd@kernel.org/
Link: https://lore.kernel.org/lkml/20240326144741.3094687-1-arnd@kernel.org/
Arnd Bergmann (4):
kbuild: turn on -Wextra by default
kbuild: remove redundant extra warning flags
kbuild: turn on -Wrestrict by default
kbuild: enable -Wformat-truncation on clang
scripts/Makefile.extrawarn | 29 +++++++++++------------------
1 file changed, 11 insertions(+), 18 deletions(-)
--
2.39.2
next reply other threads:[~2024-04-04 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 15:16 Arnd Bergmann [this message]
2024-04-04 15:16 ` [PATCH 4/4] kbuild: enable -Wformat-truncation on clang Arnd Bergmann
2024-04-08 22:00 ` [PATCH 0/4] Enable more warnings by default Justin Stitt
[not found] ` <20240404151713.3493098-2-arnd@kernel.org>
2024-04-09 16:25 ` [PATCH 1/4] kbuild: turn on -Wextra " Nathan Chancellor
2024-04-09 18:42 ` Arnd Bergmann
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=20240404151713.3493098-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=justinstitt@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/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