From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH v2] powerpc: Fix determining TI_CPU in power_save_ppc32_restore()
Date: Tue, 26 Aug 2008 14:39:28 +1000 [thread overview]
Message-ID: <1219725568.13162.122.camel@pasglop> (raw)
In-Reply-To: <1219716536-21643-1-git-send-email-galak@kernel.crashing.org>
On Mon, 2008-08-25 at 21:08 -0500, Kumar Gala wrote:
> The calculation to get TI_CPU based off of SPRG3 was just plain wrong.
> Just offset off the stack pointer (to get to thread_info) like all the
> other references to TI_CPU do.
>
> This was pointed out by Chen Gong <G.Chen@freescale.com>
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2008-08-26 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 2:08 [PATCH v2] powerpc: Fix determining TI_CPU in power_save_ppc32_restore() Kumar Gala
2008-08-26 4:39 ` Benjamin Herrenschmidt [this message]
2008-08-29 12:06 ` 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=1219725568.13162.122.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--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;
as well as URLs for NNTP newsgroup(s).