mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Daniel Bristot de Oliveira <bristot@kernel.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [GIT PULL] tracing: Fixes and clean ups for v5.14
Date: Thu, 12 Aug 2021 13:33:06 -0400	[thread overview]
Message-ID: <20210812133306.1c480741@oasis.local.home> (raw)
In-Reply-To: <CAHk-=whHxeUjaNrWOLb0qx=-nibRZzQomwkw9xMPH_aHCf=BWQ@mail.gmail.com>

On Thu, 12 Aug 2021 07:18:37 -1000
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Thu, Aug 12, 2021 at 5:29 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > - Fix warning for use of "main" variable in osnoise tracer  
> 
> Honestly, I refuse to pull this kind of inexplicable garbage.

That was my take too, when this was first addressed:

  https://lore.kernel.org/lkml/20210730204050.46975ae2@oasis.local.home/

> 
> The commit message talks about "some compilers/analyzers" without any
> explanation, and the "Link:" thing doesn't link to anything useful
> either.

I should have added the above link. :-/

Where the link in this commit was simply added by my scripts.

> 
> Those compilers/analyzers are clearly complete and utter crap, and my
> reaction is that I want a *lot* more explanation why we should care
> about other peoples crap.

I totally agree.

> 
> I do NOT want to see people caring about warnings that make no sense,
> certainly not without extensive explanations about why we should care
> about broken tools.
> 
> Fix the tool. Add a "--Wno-warn-about-stupid-issues" flag to the tool
> usage. Don't make pointless changes to the kernel to work around other
> peoples garbage.

:-) :-) :-)

I'm totally happy with this approach. I took the lazy method, and let
them change the variable.

But I'm 100% on your side of the issue. I HATE these stupid warnings.

I swear, these warnings are the gcc equivalent of spelling fixes to the
kernel. "Oh, I can get a patch into gcc via adding a new useless
warning!"

I'll drop the patch, and send you a v2.

-- Steve

  reply	other threads:[~2021-08-12 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 15:29 Steven Rostedt
2021-08-12 17:18 ` Linus Torvalds
2021-08-12 17:33   ` Steven Rostedt [this message]
2021-08-12 17:54     ` Linus Torvalds
2021-08-12 18:04       ` Randy Dunlap
2021-08-12 18:17         ` Linus Torvalds
2021-08-12 18:57           ` Randy Dunlap
2021-08-12 20:47             ` Randy Dunlap
2021-08-13  2:06               ` Linus Torvalds

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=20210812133306.1c480741@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=bristot@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=rdunlap@infradead.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

all inboxes | Powered by JetHome®