LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Anitha Chrisanthus <anitha.chrisanthus@intel.com>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: linux-next: build warning after merge of the kspp tree
Date: Mon, 6 Sep 2021 10:12:36 -0700	[thread overview]
Message-ID: <CAHk-=wgSzN4p0EW2LkA0YkRBjkOXpdaiLZMez=h=3d4Q2Gjp3A@mail.gmail.com> (raw)
In-Reply-To: <202109061000.79CF310@keescook>

On Mon, Sep 6, 2021 at 10:06 AM Kees Cook <keescook@chromium.org> wrote:
>>
> Linus, warnings are being reported (as above)

New warnings are apparently at least partly reported, but also clearly
(a) old warnings are ignored, and (b) new warnings seem to be very
spottily fixed too.

Guenter reports "pass: 89 fail: 64" for his build setups.

So the fact that *I* require a clean build, and generally have two
reject a couple of build requests every merge window because of that
clearly doesn't mean that we actually have clean builds.

I've had that "no warnings" requirement for years. And that means that
*my* build has been clean for years.

I want *all* builds to be clean, or at least as far as possible.

You should be the last to complain. You are literally the drop that
broke the camel's back. I'm done being the last guard against build
warnings.

           Linus

      reply	other threads:[~2021-09-06 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30  8:44 Stephen Rothwell
2021-08-30 23:50 ` Kees Cook
2021-08-31  0:49   ` Stephen Rothwell
2021-09-06  5:41 ` Stephen Rothwell
2021-09-06 17:06   ` Kees Cook
2021-09-06 17:12     ` Linus Torvalds [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='CAHk-=wgSzN4p0EW2LkA0YkRBjkOXpdaiLZMez=h=3d4Q2Gjp3A@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=anitha.chrisanthus@intel.com \
    --cc=gustavoars@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: build warning after merge of the kspp tree' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).