public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Guenter Roeck <linux@roeck-us.net>, Guan Xuetao <gxt@mprc.pku.edu.cn>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] unicore32: Fix build error
Date: Sun, 10 Aug 2014 17:39:43 +0200	[thread overview]
Message-ID: <53E7923F.5000008@nod.at> (raw)
In-Reply-To: <1407684595-30785-1-git-send-email-linux@roeck-us.net>

Guenther,

Am 10.08.2014 17:29, schrieb Guenter Roeck:
> unicore32 builds fail with
> 
> arch/unicore32/kernel/signal.c: In function ‘setup_frame’:
> arch/unicore32/kernel/signal.c:257: error:
> 			‘usig’ undeclared (first use in this function)
> arch/unicore32/kernel/signal.c:279: error:
> 			‘usig’ undeclared (first use in this function)
> arch/unicore32/kernel/signal.c: In function ‘handle_signal’:
> arch/unicore32/kernel/signal.c:306: warning: unused variable ‘tsk’
> arch/unicore32/kernel/signal.c: In function ‘do_signal’:
> arch/unicore32/kernel/signal.c:376: error:
> 			implicit declaration of function ‘get_signsl’
> make[1]: *** [arch/unicore32/kernel/signal.o] Error 1
> make: *** [arch/unicore32/kernel/signal.o] Error 2
> 
> Bisect points to commit 649671c90eaf ("unicore32: Use get_signal()
> signal_setup_done()").
> 
> This code never even compiled. Reverting the patch does not work,
> since previously used functions no longer exist, so try to fix it up.
> Compile tested only.

Where did you get the unicore32 cross compiler from?

The collection on kernel.org is missing it:
https://www.kernel.org/pub/tools/crosstool/

This is why it did not get any build testing.

Thanks,
//richard

> Cc: Richard Weinberger <richard@nod.at>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
>  arch/unicore32/kernel/signal.c | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/unicore32/kernel/signal.c b/arch/unicore32/kernel/signal.c
> index 780d773..7c8fb70 100644
> --- a/arch/unicore32/kernel/signal.c
> +++ b/arch/unicore32/kernel/signal.c
> @@ -254,7 +254,8 @@ static int setup_frame(struct ksignal *ksig, sigset_t *set,
>  
>  	err |= setup_sigframe(frame, regs, set);
>  	if (err == 0)
> -		err |= setup_return(regs, &ksig->ka, frame->retcode, frame, usig);
> +		err |= setup_return(regs, &ksig->ka, frame->retcode, frame,
> +				    ksig->sig);
>  
>  	return err;
>  }
> @@ -276,7 +277,8 @@ static int setup_rt_frame(struct ksignal *ksig, sigset_t *set,
>  	err |= __save_altstack(&frame->sig.uc.uc_stack, regs->UCreg_sp);
>  	err |= setup_sigframe(&frame->sig, regs, set);
>  	if (err == 0)
> -		err |= setup_return(regs, &ksig->ka, frame->sig.retcode, frame, usig);
> +		err |= setup_return(regs, &ksig->ka, frame->sig.retcode, frame,
> +				    ksig->sig);
>  
>  	if (err == 0) {
>  		/*
> @@ -303,7 +305,6 @@ static void handle_signal(struct ksignal *ksig, struct pt_regs *regs,
>  			  int syscall)
>  {
>  	struct thread_info *thread = current_thread_info();
> -	struct task_struct *tsk = current;
>  	sigset_t *oldset = sigmask_to_save();
>  	int usig = ksig->sig;
>  	int ret;
> @@ -373,7 +374,7 @@ static void do_signal(struct pt_regs *regs, int syscall)
>  	if (!user_mode(regs))
>  		return;
>  
> -	if (get_signsl(&ksig)) {
> +	if (get_signal(&ksig)) {
>  		handle_signal(&ksig, regs, syscall);
>  		return;
>  	}
> 

  reply	other threads:[~2014-08-10 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 15:29 [PATCH] unicore32: Fix build error Guenter Roeck
2014-08-10 15:39 ` Richard Weinberger [this message]
2014-08-10 16:30   ` Guenter Roeck
2014-08-11  5:04     ` 回复: " Xuetao Guan 
2014-08-15 19:38 ` Guenter Roeck
2014-08-16  0:45   ` 回复: " Xuetao Guan 
2014-08-16  2:21     ` Guenter Roeck
2014-08-18  0:26       ` 回复: " Xuetao Guan 

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=53E7923F.5000008@nod.at \
    --to=richard@nod.at \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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