From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: break out vbr register code
Date: Wed, 11 Mar 2009 08:30:19 +0000 [thread overview]
Message-ID: <20090311083019.GF6281@linux-sh.org> (raw)
In-Reply-To: <20090311081852.2041.19566.sendpatchset@rx1.opensource.se>
On Wed, Mar 11, 2009 at 05:18:52PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
>
> Add set_vbr_register(), get_vbr_register() and vbr_base
> to system.h.
>
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
> ---
>
> This register needs to be modified by the suspend code
> as well, so break it out.
>
Let's just open code the instruction instead, there is not much point in
having wrapper for a single instruction..
> arch/sh/include/asm/system.h | 19 +++++++++++++++++++
> arch/sh/kernel/traps_32.c | 13 ++-----------
> 2 files changed, 21 insertions(+), 11 deletions(-)
>
It can't be in system.h anyways, since SH-5 also uses this file.
prev parent reply other threads:[~2009-03-11 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 8:18 [PATCH] sh: break out vbr register code Magnus Damm
2009-03-11 8:30 ` Paul Mundt [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=20090311083019.GF6281@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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