public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Michal Marek <mmarek@suse.cz>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: [PATCH v3.1] kbuild: implement several W= levels
Date: Wed, 27 Apr 2011 13:35:13 +0200	[thread overview]
Message-ID: <20110427113513.GB18112@eferding.osrc.amd.com> (raw)
In-Reply-To: <20110427082555.GC5726@merkur.ravnborg.org>

On Wed, Apr 27, 2011 at 10:25:55AM +0200, Sam Ravnborg wrote:
> > - make the W= levels exclusive
> I do not see the point in this really. This is not what most people would
> expect.
> When you ask for more you get more - not something else.
> 
> We see it with verbose levels where -vv give more output than -v etc.
> 
> Anyway - the important thing is to keep the relevant warnings at W=1 level.
> Which is independendt of this change.
> So consider the input and decide - I do not want to make a fuzz about it.

I know, -vv.. increases verbosity is probably part of old unix tradition
or common sense but it doesn't make much sense in this case, IMHO. When
I use this, I want to see what the most relevant warnings are, maybe
have a crack at them to fix them, and _then_ look at the less important
ones (for an arbitrary definition of important warnings).

If we do this inclusive, then W=2 dumps the, let's call it, level 1
_plus_ the new level 2 warnings, polluting the output with something
I've already seen, but only partially. And then I start to think, did
I see this one already, didn't I, which was it? By the time you enable
W=3, the output becomes pretty useless. For example, W=3 generates 190+
MB logfile here only with level 3 warnings. Now imagine all 3 levels
combined.

Dividing the output by level of importance doesn't have this problem and
is much more workable, IMHO.

But this is just my use case, it could be that I'm completely alone on
this one. I'd love to hear what other people think.

FWIW, we might even make this behavior configurable by having

make W=1o

meaning level 1 warnings only or whatever sick idea we come up with
eventually.

;-)

Thanks.

-- 
Regards/Gruss,
Boris.

  reply	other threads:[~2011-04-27 11:35 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 21:39 [RFC PATCH] kbuild: implement several W= levels Sam Ravnborg
2011-04-21 21:58 ` Joe Perches
2011-04-21 22:56   ` Stratos Psomadakis
2011-04-21 22:06 ` Stratos Psomadakis
2011-04-22  1:28   ` Sam Ravnborg
2011-04-22  7:38 ` [RFC PATCH v2] " Sam Ravnborg
2011-04-22  8:19 ` [RFC PATCH] " Borislav Petkov
2011-04-22 10:15   ` Sam Ravnborg
2011-04-22 10:20     ` Borislav Petkov
2011-04-22 10:46       ` [PATCH v3] " Borislav Petkov
2011-04-22 11:09         ` Sam Ravnborg
2011-04-22 17:50           ` [PATCH v3.1] " Borislav Petkov
2011-04-26 19:52             ` Michal Marek
2011-04-26 20:43               ` Borislav Petkov
2011-04-27  8:22                 ` Sam Ravnborg
2011-04-27  8:25             ` Sam Ravnborg
2011-04-27 11:35               ` Borislav Petkov [this message]
2011-04-27 20:15                 ` [PATCH v3.2] " Borislav Petkov
2011-04-27 20:21                   ` Joe Perches
2011-04-27 20:46                     ` Sam Ravnborg
2011-04-27 20:46                   ` Sam Ravnborg
2011-04-28 16:18                   ` Michal Marek
2011-04-28  0:25                 ` [PATCH v3.1] " Valdis.Kletnieks
2011-04-28 16:24                   ` Michal Marek
2011-04-28 17:59                     ` Valdis.Kletnieks
2011-04-29 13:31                       ` [PATCH] kbuild: Allow to combine multiple " Michal Marek
2011-04-29 17:43                         ` Sam Ravnborg
2011-04-29 18:13                         ` Arnaud Lacombe
2011-04-29 18:27                           ` Valdis.Kletnieks
2011-04-29 18:29                         ` Valdis.Kletnieks
2011-05-02 15:38                         ` Michal Marek
2011-05-02 15:53                           ` Arnaud Lacombe
2011-05-02 16:05                             ` Michal Marek
2011-05-02 16:17                               ` Arnaud Lacombe
2011-05-02 16:16                         ` Américo Wang
2011-05-02 17:07                           ` Sam Ravnborg
2011-05-02 17:34                             ` Arnaud Lacombe
2011-05-02 18:03                               ` boris
2011-05-02 18:45                                 ` Arnaud Lacombe
2011-05-02 18:51                                   ` boris
2011-05-02 20:35                                   ` Michal Marek
2011-04-27  8:27         ` [PATCH v3] kbuild: implement several " Geert Uytterhoeven

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=20110427113513.GB18112@eferding.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=davej@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.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