All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Spencer <maillist-mdadm@barfooze.de>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] mdadm: fix portability issues encountered while building against musl libc
Date: Mon, 11 Feb 2013 20:34:59 +0100	[thread overview]
Message-ID: <511947E3.9040400@barfooze.de> (raw)
In-Reply-To: <20130210154548.0ad0c36d@notabene.brown>

On 02/10/2013 05:45 AM, NeilBrown wrote:
>
> Hi,
>   I've applied this one and the GCC #ifdef - thanks.

thanks!

>
>   I haven't applied the last one, but not because I don't appreciate being
>   called insane :-)

he he :)

>
>   I like having -Werror as it encourages people to report any warnings they
>   get, and it keeps me "honest".

well, i dont think anyone except of the author(s) wants that flag 
activated by default so that they can find warnings without looking to 
closely.

>   If it is a problem for you, you can easily
>     make CWFLAGS=

i know, but "broken-by-default" is not a very friendly setting.
there are quite a couple of warnings GCC emits that are simply bogus.
i'd rather if the one that actually wants this hardcore setting uses 
make CWFLAGS=-Werror (or make FATAL=1) instead of forcing his policy on 
all users.

>
>   or set the C Warning FLAGS to whatever you like - they are deliberately kept
>   separate from other CFLAGS.
>
> Thanks,
> NeilBrown


thanks,
--JS

      reply	other threads:[~2013-02-11 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 23:15 [PATCH] mdadm: fix portability issues encountered while building against musl libc John Spencer
2013-02-09 23:40 ` Joseph Glanville
2013-02-10  4:45 ` NeilBrown
2013-02-11 19:34   ` John Spencer [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=511947E3.9040400@barfooze.de \
    --to=maillist-mdadm@barfooze.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.