From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/3] mpc83xx: Power Management support
Date: Wed, 02 Jul 2008 11:38:12 -0500 [thread overview]
Message-ID: <486BAEF4.9000904@freescale.com> (raw)
In-Reply-To: <AEE09588-1480-450B-BEDF-237E2D59D3D0@kernel.crashing.org>
Kumar Gala wrote:
> If we are going to allocate space for save area like this, can't we do
> this in C code. Its less error prone and easier to extend over time. I
> know the powermac code does something similar but it places the save
> area on the stack.
Then we'd have to split it between things that can be saved from C
versus things that can't (gpregs, cr, lr, etc), or mess around with
exposing struct offsets to asm code. I think it's just easier to do it
this way.
-Scott
next prev parent reply other threads:[~2008-07-02 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 21:50 [PATCH 1/3] mpc83xx: Power Management support Scott Wood
2008-06-26 13:43 ` Kumar Gala
2008-06-26 14:07 ` Scott Wood
2008-06-26 14:39 ` Liu Dave
2008-06-26 14:54 ` Kumar Gala
2008-07-02 16:03 ` Kumar Gala
2008-07-02 16:38 ` Scott Wood [this message]
2008-07-02 17:06 ` Kumar Gala
2008-07-02 17:12 ` Scott Wood
2008-07-02 17:37 ` Kumar Gala
2008-07-02 17:46 ` Scott Wood
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=486BAEF4.9000904@freescale.com \
--to=scottwood@freescale.com \
--cc=galak@kernel.crashing.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 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.