All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] automake: add -Werror to CFLAGS
Date: Tue, 17 Apr 2012 11:00:07 +0530	[thread overview]
Message-ID: <4F8CFFDF.9010509@suse.com> (raw)
In-Reply-To: <CAH2r5mu5h+QWq8a3jjE6HBZUYvyYW_a74vPgg0nOqhRgzwU+HA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 04/17/2012 03:03 AM, Steve French wrote:
> Good idea - thx
> 
> On Mon, Apr 16, 2012 at 1:13 PM, Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org> wrote:
>> With the recent patch to fix the warnings in asn1.c, cifs-utils now
>> builds without any warnings. Ban them henceforth by adding -Werror for
>> builds.
>>
>> Signed-off-by: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
>> ---
>>  Makefile.am |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/Makefile.am b/Makefile.am
>> index 17ad8e1..d95142a 100644
>> --- a/Makefile.am
>> +++ b/Makefile.am
>> @@ -1,4 +1,4 @@
>> -AM_CFLAGS = -Wall -Wextra
>> +AM_CFLAGS = -Wall -Wextra -Werror
>>  ACLOCAL_AMFLAGS = -I aclocal

Any thoughts on making a similar change to the cifs kernel module
Makefile as well?

I see from the sources that some of arch/ code, a few drivers and perf
are already using it. Perf Makefile treats warnings as errors unless
directed not to and there is a flag to disable treating any warnings as
error (for e.g. by passing WERROR=0).


Suresh

  parent reply	other threads:[~2012-04-17  5:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 18:13 [PATCH] automake: add -Werror to CFLAGS Jeff Layton
     [not found] ` <1334600010-27430-1-git-send-email-jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2012-04-16 21:33   ` Steve French
     [not found]     ` <CAH2r5mu5h+QWq8a3jjE6HBZUYvyYW_a74vPgg0nOqhRgzwU+HA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-17  5:30       ` Suresh Jayaraman [this message]
     [not found]         ` <4F8CFFDF.9010509-IBi9RG/b67k@public.gmane.org>
2012-04-17 15:28           ` Steve French
     [not found]             ` <CAH2r5mupTfeFza=LrtsOQn95RxyQOS7G=xYFNsBF6FFhGvyxzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-17 15:56               ` Suresh Jayaraman
2012-04-18 19:54   ` Jeff Layton

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=4F8CFFDF.9010509@suse.com \
    --to=sjayaraman-ibi9rg/b67k@public.gmane.org \
    --cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.