[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250612080256.10868Ace-hca@linux.ibm.com>
Date: Thu, 12 Jun 2025 10:02:56 +0200
From: Heiko Carstens <hca@...ux.ibm.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for v6.16-rc1
On Thu, Jun 12, 2025 at 10:42:40AM +0900, Masahiro Yamada wrote:
> On Wed, Jun 11, 2025 at 11:24 PM Arnd Bergmann <arnd@...db.de> wrote:
> > I think this makes sense in general, but the output here is
> > excessive if it leads to users no longer wanting to enable W=1.
> >
> > There are other warnings that I think should be enabled at the
> > W=1 level (e.g. -Wformat-security) and eventually by default,
> > but that are still too noisy at that level.
> >
> > My own cutoff would be at a few hundred warnings in allmodconfig
> > builds if there is an effort to reduce it further, but it seems
> > that this one is still at a few thousand, which does not seem ok.
> >
> > Arnd
>
> Then, what to do? Downgrade to W=2?
>
> I think nobody cares about W=2 builds,
> and the problem of all C files including <linux/export.h>
> would remain forever.
For example you could provide a method to opt-out, similar to
RECORDMCOUNT_WARN, except that the default would be enabled.
This option would go away in the (near?) future again, as soon
as everything has been addressed.
Powered by blists - more mailing lists