All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: josh@joshtriplett.org
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] sparse: Make -Werror turn warnigns into errors
Date: Wed, 3 Sep 2014 21:08:56 +0200	[thread overview]
Message-ID: <20140903190856.GC18161@pox.localdomain> (raw)
In-Reply-To: <20140903185939.GA24390@cloud>

On 09/03/14 at 11:59am, josh@joshtriplett.org wrote:
> This seems reasonable.  Sparse refrains from showing further warnings
> after an error, but this turns warnings into errors, so they'll still
> show up.
> 
> Not needed for this patch, but would you consider adding
> -Werror=specific-warning support too?  (That'll need some careful
> thought about the no-warnings-after-error logic, which may or may not
> make sense.)

Sure. I think that is definitely desirable. I wanted to collect
feedback on the behavioural change first using a minimal patch.

  reply	other threads:[~2014-09-03 19:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 18:54 [PATCH] sparse: Make -Werror turn warnigns into errors Thomas Graf
2014-09-03 18:59 ` josh
2014-09-03 19:08   ` Thomas Graf [this message]
2014-09-24 12:31     ` Sparse maintainership (was: [PATCH] sparse: Make -Werror turn warnigns into errors) Thomas Graf
2014-09-24 15:05       ` Christopher Li
2014-09-24 15:24 ` [PATCH] sparse: Make -Werror turn warnigns into errors Christopher Li
2014-09-24 15:42   ` Thomas Graf
2014-09-24 23:16     ` Christopher Li
2014-09-25  2:27       ` Christopher Li
2014-09-25  2:46       ` Christopher Li
2014-09-25  8:12         ` Thomas Graf

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=20140903190856.GC18161@pox.localdomain \
    --to=tgraf@suug.ch \
    --cc=josh@joshtriplett.org \
    --cc=linux-sparse@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.