Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: mark@codesourcery.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Fix MT MAC register access
Date: Tue, 23 May 2006 00:25:00 -0000	[thread overview]
Message-ID: <20060522172111.089d1d69@ironwood.lan> (raw)
In-Reply-To: <200604120326.k3C3QAZN000703@sethra.codesourcery.com>

On Tue, 11 Apr 2006 20:26:10 -0700
Mark Mitchell <mark@codesourcery.com> wrote:

> 2006-04-11  Mark Mitchell  <mark@codesourcery.com>
> 
> 	* mt-tdep.c (mt_gdb_regnums): Define
> 	MT_COPRO_PSEUDOREG_MAC_REGNUM.
> 	(mt_register_name): Use it.
> 	(mt_copro_register_type): Likewise.
> 	(mt_register_type): Likewise.
> 	(mt_pseudo_register_read): Likewise.  Read the MAC register, not
> 	the coprocessor register.
> 	(mt_pseudo_register_write): Likewise.

Okay.  (Sorry for the late response on this one.)

Kevin


      reply	other threads:[~2006-05-23  0:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12  3:26 Mark Mitchell
2006-05-23  0:25 ` Kevin Buettner [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=20060522172111.089d1d69@ironwood.lan \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark@codesourcery.com \
    /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