From: Manish Ahuja <ahuja@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Manish Ahuja <mahuja@us.ibm.com>,
LinuxPPC-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] [RFC] Pass a valid token to rats_call() in phyp-dump code.
Date: Tue, 16 Dec 2008 12:38:48 -0600 [thread overview]
Message-ID: <4947F5B8.4050500@austin.ibm.com> (raw)
In-Reply-To: <20081216043429.GC14890@ozlabs.org>
Yes,
That is required. It is in the patches that I sent to Ben, Paul & Brad.
I just waiting to post it with other patches.
Acked-by: Manish Ahuja <mahujam@gmail.com>
Tony Breeds wrote:
> ibm_configure_kernel_dump, is passed as the token to rtas_call() but I
> cannot see where it is initialised. Set it to something sane?
>
> Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
> ---
> arch/powerpc/platforms/pseries/phyp_dump.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/platforms/pseries/phyp_dump.c b/arch/powerpc/platforms/pseries/phyp_dump.c
> index 16e659a..6cf35cd 100644
> --- a/arch/powerpc/platforms/pseries/phyp_dump.c
> +++ b/arch/powerpc/platforms/pseries/phyp_dump.c
> @@ -414,6 +414,8 @@ static int __init phyp_dump_setup(void)
> of_node_put(rtas);
> }
>
> + ibm_configure_kernel_dump = rtas_token("ibm,configure-kernel-dump");
> +
> print_dump_header(dump_header);
> dump_area_length = init_dump_header(&phdr);
> /* align down */
--
--
Manish Ahuja
Linux RAS Engineer.
IBM Linux Technology Center
mahuja@us.ibm.com
512-838-1928, t/l 678-1928.
next prev parent reply other threads:[~2008-12-16 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 4:34 [PATCH] [RFC] Pass a valid token to rats_call() in phyp-dump code Tony Breeds
2008-12-16 5:12 ` Nathan Lynch
2008-12-16 18:38 ` Manish Ahuja [this message]
2008-12-17 12:47 ` Josh Boyer
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=4947F5B8.4050500@austin.ibm.com \
--to=ahuja@austin.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahuja@us.ibm.com \
--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 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.