From: Paul Mackerras <paulus@samba.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, <linux-kernel@vger.kernel.org>
Subject: Re: Please pull from 'for_paulus' branch of powerpc
Date: Fri, 5 May 2006 08:49:29 +1000 [thread overview]
Message-ID: <17498.34041.993647.189930@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0605041622180.3700-100000@gate.crashing.org>
Kumar Gala writes:
> Please pull from 'for_paulus' branch of
> master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git
> --- a/arch/powerpc/kernel/setup_32.c
> +++ b/arch/powerpc/kernel/setup_32.c
> @@ -236,6 +236,7 @@ arch_initcall(ppc_init);
> void __init setup_arch(char **cmdline_p)
> {
> extern void do_init_bootmem(void);
> + extern void setup_panic(void);
Urk.
> @@ -285,6 +286,9 @@ #endif
> /* reboot on panic */
> panic_timeout = 180;
>
> + if (ppc_md.panic)
> + setup_panic();
Since no 32-bit platform sets ppc_md.panic AFAICS, I guess this
doesn't need to be pushed into 2.6.17. Please redo with setup_panic
declared in a header file.
Paul.
next prev parent reply other threads:[~2006-05-04 22:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 21:28 Please pull from 'for_paulus' branch of powerpc Kumar Gala
2006-05-04 22:09 ` Segher Boessenkool
2006-05-04 22:10 ` Kumar Gala
2006-05-04 22:36 ` Segher Boessenkool
2006-05-04 22:49 ` Paul Mackerras [this message]
2006-05-05 4:59 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 6:13 Zhang Wei-r63237
2006-06-29 3:33 Zhang Wei-r63237
2006-06-29 5:08 ` Kumar Gala
2006-06-29 9:10 ` Benjamin Herrenschmidt
2006-06-28 6:26 Zhang Wei-r63237
2006-06-28 13:19 ` Kumar Gala
2006-06-28 6:01 Kumar Gala
2006-06-28 22:44 ` Jon Loeliger
2006-04-04 21:14 Kumar Gala
2006-04-05 0:28 ` Stephen Rothwell
2006-04-05 1:23 ` Kumar Gala
2006-04-05 3:05 ` Stephen Rothwell
2006-04-05 4:33 ` Kumar Gala
2006-03-31 5:43 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=17498.34041.993647.189930@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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