Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] new frame code for h8300 target
Date: Thu, 17 Feb 2005 03:18:00 -0000	[thread overview]
Message-ID: <20050217003720.GB9895@nevyn.them.org> (raw)
In-Reply-To: <m2r7jhlsjo.wl%ysato@users.sourceforge.jp>

On Wed, Feb 16, 2005 at 01:03:07AM +0900, Yoshinori Sato wrote:
> At Mon, 14 Feb 2005 21:02:48 -0500,
> Andrew Cagney wrote:
> > 
> > [1  <text/plain; ISO-8859-1 (7bit)>]
> > Just FYI, the changes to resurect h8300-tdep.c and h8300.mt are ok (I 
> > see the're already committed).  However the change to resurect 
> > config/h8300/tm-h8300.h isn't - the h8300 is now considered to be a new 
> > architecture and any new architecture is required to be pure multi-arch 
> > (i.e., no tm-*.h file).
> > 
> > Looking forward to patches that fix that.
> > 
> > In the mean time I've committed the attached,
> > Andrew
> 
> I made sure.
> Because a section depending on tm-h8300.h seems to be left, 
> I will correct it.

I guess you mean this patch:

2005-02-16  Yoshinori Sato  <ysato@users.sourceforge.jp>

        * remote-e7000.c: unuse TM_FILE defined macro.
        (e7000_fetch_registers)
        (e7000_store_registers)
        (e7000_wait): delete NUM_REALREGS.
        * remote-hms.c: move TM_FILE macro.
        (CCR_REGNO): move define from tm-h8300.h.

I didn't see this patch posted to gdb-patches; please always post
patches to the mailing list before committing them.

Who should be listed as the maintainer for the h8300 port?  It is still
listed as deleted in MAINTAINERS.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-02-17  0:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14 16:23 Yoshinori Sato
2004-11-15 23:43 ` Andrew Cagney
2005-01-13 17:18   ` Yoshinori Sato
2005-01-13 21:15     ` Andrew Cagney
     [not found]       ` <m2k6pyqsss.wl%ysato@users.sourceforge.jp>
     [not found]         ` <4200FA23.3070602@gnu.org>
     [not found]           ` <m28y66ie6a.wl%ysato@users.sourceforge.jp>
2005-02-09 16:00             ` Andrew Cagney
2005-02-09 17:02               ` Yoshinori Sato
2005-02-09 17:05                 ` Andrew Cagney
2005-02-10  9:55                   ` Yoshinori Sato
2005-02-15 10:03                     ` Andrew Cagney
2005-02-15 20:10                       ` Yoshinori Sato
2005-02-16 17:35                         ` Andrew Cagney
2005-02-17  3:18                         ` Daniel Jacobowitz [this message]
2005-02-17 16:14                           ` Andrew Cagney
2004-11-16  6:39 Asgari J. Jinia
2004-11-16 18:43 ` Andrew Cagney

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=20050217003720.GB9895@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ysato@users.sourceforge.jp \
    /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