All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] powerpc: Add configurable -Werror for arch/powerpc
Date: Thu, 18 Jun 2009 16:22:18 +0200	[thread overview]
Message-ID: <200906181622.18349.arnd@arndb.de> (raw)
In-Reply-To: <ed82fe3e0906150754w125c6283q2468213b59c7f114@mail.gmail.com>

On Monday 15 June 2009, Timur Tabi wrote:
> On Mon, Jun 15, 2009 at 2:50 AM, Michael Ellerman<michael@ellerman.id.au> wrote:
> > arch/powerpc/platforms/chrp/setup.c:378: error: the frame size of 1040 bytes is larger than 1024 bytes
> 
> What's so bad about a frame size larger than 1024?
> 

It's not necessarily a bug, but all frame sizes in the call chain
combined must never exceed the kernel stack size. 1024 is an
arbitrary limit that we warn about for a single function, because
it's likely that things will break if you have more than one of these.

	Arnd <><

  reply	other threads:[~2009-06-18 14:23 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
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 [this message]
  -- 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=200906181622.18349.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.com \
    /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.