Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [GIT PULL] Kbuild updates for v6.16-rc1
Date: Wed, 11 Jun 2025 05:59:54 -0700	[thread overview]
Message-ID: <aEl9yiUdQLetv_T_@google.com> (raw)
In-Reply-To: <20250611075533.8102A57-hca@linux.ibm.com>

On Wed, Jun 11, 2025, Heiko Carstens wrote:
> On Sun, Jun 08, 2025 at 01:41:18AM +0900, Masahiro Yamada wrote:
> > Kbuild updates for v6.16
> > 
> >  - Add support for the EXPORT_SYMBOL_GPL_FOR_MODULES() macro, which exports a
> >    symbol only to specified modules
> > 
> >  - Improve ABI handling in gendwarfksyms
> > 
> >  - Forcibly link lib-y objects to vmlinux even if CONFIG_MODULES=n
> > 
> >  - Add checkers for redundant or missing <linux/export.h> inclusion
> 
> As you write in commit a934a57a42f6 ("scripts/misc-check: check missing
> #include <linux/export.h> when W=1") this adds now 4000+ extra warnings
> for W=1 builds, which makes such builds more or less useless for me.
> 
> Also the commit only describes what you want to achieve, but not why.
> I can only guess that you want to reduce header dependencies(?).
> 
> Don't get me wrong, I can address all of this trivial churn for s390, however
> enforcing so many extra warnings to everyone with W=1 builds doesn't look like
> the right approach to me.

+1.  This seems like a recipe for an endless game of whack-a-mole.

  reply	other threads:[~2025-06-11 12:59 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 [this message]
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

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=aEl9yiUdQLetv_T_@google.com \
    --to=seanjc@google.com \
    --cc=arnd@arndb.de \
    --cc=hca@linux.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox