mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	workflows@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH v2 3/4] scripts/misc-check: check missing #include <linux/export.h> when W=1
Date: Thu, 19 Jun 2025 09:26:11 -0700	[thread overview]
Message-ID: <20250619092611.07d2feb8@kernel.org> (raw)
In-Reply-To: <CAK7LNARJdVRcUCKo2zEfJr_0Dc-1fzkjf01OsDpDQLH2+wZHCg@mail.gmail.com>

On Fri, 20 Jun 2025 01:13:28 +0900 Masahiro Yamada wrote:
> > IIUC you made the kernel spew nearly 5000 warnings on every W=1 build
> > to "encourage" others to help fix a fairly innocuous problem.
> > I appreciate the work that goes into separating the headers but it's
> > hardly urgent enough to force others to scroll thru 5k warnings.
> >
> > Please LMK if I'm missing some context here, otherwise I think this is
> > quite antisocial behavior, and the warnings should go back to W=2 until
> > someone actually cares to fix most of them.
> >
> > Happy to hear from others.. CC: workflows  
> 
> Please see commit a6a7946bd691940cfe7289ae6dfb1f077516df72

Thank you.

  reply	other threads:[~2025-06-19 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-01 13:31 [PATCH v2 1/4] kbuild: move W=1 check for scripts/misc-check to top-level Makefile Masahiro Yamada
2025-06-01 13:31 ` [PATCH v2 2/4] scripts/misc-check: add double-quotes to satisfy shellcheck Masahiro Yamada
2025-06-01 13:31 ` [PATCH v2 3/4] scripts/misc-check: check missing #include <linux/export.h> when W=1 Masahiro Yamada
2025-06-04  4:52   ` Masahiro Yamada
2025-06-19 16:01   ` Jakub Kicinski
2025-06-19 16:13     ` Masahiro Yamada
2025-06-19 16:26       ` Jakub Kicinski [this message]
2025-06-01 13:31 ` [PATCH v2 4/4] scripts/misc-check: check unnecessary " Masahiro Yamada
2025-06-02 22:06 ` [PATCH v2 1/4] kbuild: move W=1 check for scripts/misc-check to top-level Makefile Nathan Chancellor

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=20250619092611.07d2feb8@kernel.org \
    --to=kuba@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=workflows@vger.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
all inboxes | Powered by JetHome®