From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Renninger <trenn@suse.de>, Greg KH <greg@kroah.com>,
Jason Baron <jbaron@redhat.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree (driver-core tree related)
Date: Mon, 13 Sep 2010 22:14:58 -0700 [thread overview]
Message-ID: <4C8F04D2.8020206@oracle.com> (raw)
In-Reply-To: <20100914143159.dca830f0.sfr@canb.auug.org.au>
On 09/13/10 21:31, Stephen Rothwell wrote:
> Hi Thomas,
>
> On Mon, 13 Sep 2010 21:26:13 +0200 Thomas Renninger <trenn@suse.de> wrote:
>>
>> On Monday 13 September 2010 17:51:55 Randy Dunlap wrote:
>>> On Mon, 6 Sep 2010 19:34:04 -0700 Greg KH wrote:
>>>
>>>> On Tue, Sep 07, 2010 at 11:54:26AM +1000, Stephen Rothwell wrote:
>>>>>
>>>>> After merging the final tree, today's linux-next build (powerpc
>>>>> allnoconfig) produced this warning:
>>>>>
>>>>> kernel/params.c: In function 'parse_args':
>>>>> kernel/params.c:233: warning: the frame size of 1032 bytes is larger than 1024 bytes
>>>>>
>>>>> Introduced by commit 32e6407e9361cd1aac39ff6b744cad48d1802a08 ("Dynamic
>>>>> Debug: Introduce global fake module param module.ddebug") which added a
>>>>> 1024 byte array to the stack ...
>>>>
>>>> Wierd, why didn't this show up yesterday? The patch was in that tree
>>>> then, right?
>>>>
>>>> Thomas, care to fix this up?
>>>
>>> ping. Is Thomas around??
>> Yep, sorry for not responding.
>>
>> I tried to reproduce this on ppc64, but above file compiled without
>> warning with dynamic debug set. Thus I thought this still came from the
>> old patch.
>
> The report is for a powerpc allnoconfig build (see above) i.e. ppc32.
It also happens on x86_32 (i386).
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-09-14 5:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 1:54 linux-next: build warning after merge of the final tree (driver-core tree related) Stephen Rothwell
2010-09-07 2:34 ` Greg KH
2010-09-07 7:05 ` Stephen Rothwell
2010-09-13 15:51 ` Randy Dunlap
2010-09-13 19:26 ` Thomas Renninger
2010-09-13 20:57 ` Greg KH
2010-09-14 7:22 ` Thomas Renninger
2010-09-14 13:28 ` Greg KH
2010-09-14 4:31 ` Stephen Rothwell
2010-09-14 5:14 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 7:32 Stephen Rothwell
2013-06-06 7:59 ` Ming Lei
2013-06-19 8:00 Stephen Rothwell
2013-06-19 14:38 ` Greg KH
2013-06-20 1:34 ` Ming Lei
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=4C8F04D2.8020206@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=greg@kroah.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trenn@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.