qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: gerg@snapgear.com
Cc: Greg Ungerer <gerg@uclinux.org>,
	qemu-devel@nongnu.org, paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH v2] m68k: implement move to/from usp register instruction
Date: Fri, 14 Sep 2012 12:38:56 -0700	[thread overview]
Message-ID: <505387D0.1070906@twiddle.net> (raw)
In-Reply-To: <1347579475-9293-1-git-send-email-gerg@snapgear.com>

On 09/13/2012 04:37 PM, gerg@snapgear.com wrote:
> From: Greg Ungerer <gerg@uclinux.org>
> 
> Fill out the code support for the move to/from usp instructions. They are
> being decoded, but there is no code to support their actions. So add it.
> 
> Current versions of Linux running on the ColdFire 5208 use these instructions.
> 
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>

Reviewed-by: Richard Henderson <rth@twiddle.net>


r~

      reply	other threads:[~2012-09-14 19:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 23:37 [Qemu-devel] [PATCH v2] m68k: implement move to/from usp register instruction gerg
2012-09-14 19:38 ` Richard Henderson [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=505387D0.1070906@twiddle.net \
    --to=rth@twiddle.net \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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).