From: Matt Fleming <matt.fleming@intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
Chris Zankel <chris@zankel.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] xtensa: fix build failure in xtensa/kernel/signal.c
Date: Thu, 19 Apr 2012 08:45:25 +0100 [thread overview]
Message-ID: <1334821525.26997.39.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1334782256-351-1-git-send-email-paul.gortmaker@windriver.com>
On Wed, 2012-04-18 at 16:50 -0400, Paul Gortmaker wrote:
> Caused by commit 3785006ac3c8941feb63097c416de92114a6bc39
>
> "xtensa: don't mask signals if we fail to setup signal stack"
>
> It assigns a return value to "ret", but there is no such variable
> anywhere in scope. Create one.
>
> Cc: Matt Fleming <matt.fleming@intel.com>
> Cc: Oleg Nesterov <oleg@redhat.com>
> Cc: Chris Zankel <chris@zankel.net>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> diff --git a/arch/xtensa/kernel/signal.c b/arch/xtensa/kernel/signal.c
> index b69b000..d78869a 100644
> --- a/arch/xtensa/kernel/signal.c
> +++ b/arch/xtensa/kernel/signal.c
> @@ -496,6 +496,7 @@ int do_signal(struct pt_regs *regs, sigset_t *oldset)
> signr = get_signal_to_deliver(&info, &ka, regs, NULL);
>
> if (signr > 0) {
> + int ret;
>
> /* Are we from a system call? */
>
Whoops! Thanks Paul, that's my bad. Looks like I went code-blind after
making the same kinds of changes to lots of different architectures.
I've added Andrew to the Cc list since he picked up the last set of
xtensa signal patches.
next prev parent reply other threads:[~2012-04-19 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 20:50 Paul Gortmaker
2012-04-19 7:45 ` Matt Fleming [this message]
2012-04-19 12:46 ` Paul Gortmaker
2012-04-19 13:02 ` Matt Fleming
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=1334821525.26997.39.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt.fleming@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paul.gortmaker@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®