All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for v6.16-rc1
Date: Thu, 12 Jun 2025 10:02:56 +0200	[thread overview]
Message-ID: <20250612080256.10868Ace-hca@linux.ibm.com> (raw)
In-Reply-To: <CAK7LNAShTuuxL6+foeQBTg4Nf581Q3vy38XGuXRk4hFvEAWjig@mail.gmail.com>

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@arndb.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.

      parent reply	other threads:[~2025-06-12  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07 16:41 [GIT PULL] Kbuild updates for v6.16-rc1 Masahiro Yamada
2025-06-07 19:07 ` pr-tracker-bot
2025-06-11  7:55 ` Heiko Carstens
2025-06-11 12:59   ` Sean Christopherson
2025-06-11 13:32   ` Masahiro Yamada
2025-06-11 14:24     ` Arnd Bergmann
2025-06-12  1:42       ` Masahiro Yamada
2025-06-12  8:01         ` Arnd Bergmann
2025-06-12 14:29           ` Heiko Carstens
2025-06-12 16:10             ` Masahiro Yamada
2025-06-12 15:39           ` Masahiro Yamada
2025-06-12  8:02         ` Heiko Carstens [this message]

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=20250612080256.10868Ace-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=arnd@arndb.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.