From: Kumar Gala <galak@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: Fix ARCH=ppc builds
Date: Thu, 19 Jul 2007 22:10:36 -0500 [thread overview]
Message-ID: <A2827AAE-077D-4DEC-A4FD-2E2CD8B4B809@kernel.crashing.org> (raw)
In-Reply-To: <20070720031110.GP3925@crusty.rchland.ibm.com>
On Jul 19, 2007, at 10:11 PM, Josh Boyer wrote:
> The recent signal rework broke ARCH=3Dppc builds with the following =20=
> error:
>
> CC arch/powerpc/kernel/signal.o
> arch/powerpc/kernel/signal.c: In function =91do_signal=92:
> arch/powerpc/kernel/signal.c:142: error: implicit declaration of =20
> function =91set_dabr=92
> make[1]: *** [arch/powerpc/kernel/signal.o] Error 1
>
> The patch below fixes it by including a function prototype in
> asm-ppc/system.h
>
> Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Acked-by: Kumar Gala <galak@kernel.crashing.org>
(Bet me to posting this :)
> diff --git a/include/asm-ppc/system.h b/include/asm-ppc/system.h
> index f1311a8..cc45780 100644
> --- a/include/asm-ppc/system.h
> +++ b/include/asm-ppc/system.h
> @@ -54,6 +54,7 @@ extern void show_regs(struct pt_regs * regs);
> extern void flush_instruction_cache(void);
> extern void hard_reset_now(void);
> extern void poweroff_now(void);
> +extern int set_dabr(unsigned long dabr);
> #ifdef CONFIG_6xx
> extern long _get_L2CR(void);
> extern long _get_L3CR(void);
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
prev parent reply other threads:[~2007-07-20 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 3:11 Fix ARCH=ppc builds Josh Boyer
2007-07-20 3:10 ` Kumar Gala [this message]
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=A2827AAE-077D-4DEC-A4FD-2E2CD8B4B809@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox