All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: BenjaminHerrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Add configurable -Werror for arch/powerpc
Date: Mon, 15 Jun 2009 17:50:41 +1000	[thread overview]
Message-ID: <1245052241.7705.78.camel@concordia> (raw)
In-Reply-To: <adf502e7c85161d77fdcaca24f55ba6b418c7f04.1244616523.git.michael@ellerman.id.au>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

On Wed, 2009-06-10 at 16:48 +1000, Michael Ellerman wrote:
> Add the option to build the code under arch/powerpc with -Werror.
> 
> The intention is to make it harder for people to inadvertantly introduce
> warnings in the arch/powerpc code. It needs to be configurable so that
> if a warning is introduced, people can easily work around it while it's
> being fixed.
> 
> The option is a negative, ie. don't enable -Werror, so that it will be
> turned on for allyes and allmodconfig builds.
> 
> The default is n, in the hope that developers will build with -Werror,
> that will probably lead to some build breaks, I am prepared to be flamed.

Currently this appears to break only one of the defconfigs, chrp32.

http://kisskb.ellerman.id.au/kisskb/head/1907/

And that's a legitimate error AFAICT:

arch/powerpc/platforms/chrp/setup.c:378: error: the frame size of 1040 bytes is larger than 1024 bytes

From:

367 void
368 chrp_event_scan(unsigned long unused)
369 {
370         unsigned char log[1024];
371         int ret = 0;


cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-15  7:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10  6:48 [PATCH] powerpc: Add configurable -Werror for arch/powerpc Michael Ellerman
2009-06-15  7:50 ` Michael Ellerman [this message]
2009-06-15  9:40   ` Benjamin Herrenschmidt
2009-06-15 12:36     ` Michael Ellerman
2009-06-15 21:23       ` Benjamin Herrenschmidt
2009-06-15 14:54   ` Timur Tabi
2009-06-18 14:22     ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2009-04-07  2:00 Michael Ellerman
2009-04-07  2:27 ` Olof Johansson
2009-04-07  2:28   ` David Miller
2009-04-07  2:37     ` Olof Johansson
2009-04-07  3:01   ` Michael Ellerman
2009-04-07 14:11     ` Olof Johansson
2009-04-07  7:41   ` Geert Uytterhoeven
2009-04-07  7:50     ` Stephen Rothwell
2009-04-07 15:05 ` Kumar Gala
2009-04-06  4:18 Michael Ellerman
2009-04-06 12:55 ` Kumar Gala

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=1245052241.7705.78.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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.