From: Eli Zaretskii <eliz@gnu.org>
To: Michael Eager <eager@eagercon.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [PATCH] Support for Xilinx MicroBlaze
Date: Tue, 06 Oct 2009 07:14:00 -0000 [thread overview]
Message-ID: <83ab05nggh.fsf@gnu.org> (raw)
In-Reply-To: <4ACA9EE8.1040007@eagercon.com>
> Date: Mon, 05 Oct 2009 18:35:36 -0700
> From: Michael Eager <eager@eagercon.com>
> CC: Joel Brobecker <brobecker@adacore.com>, Eli Zaretskii <eliz@gnu.org>
>
> Revised patch. I believe that I have addressed all of the comments.
>
> 2009-10-05 Michael Eager <eager@eagercon.com>
>
> * config/djgpp/fnchange.lst: Add translations for cpu-microblaze.c,
> elf32-microblaze.c, microblaze-rom.c, microblaze-linux-tdep.c,
> microblaze-tdep.h, microblaze-tdep.c, microblaze-opc.h, microblaze-opcm.h,
> microblaze-dis.c, microblaze-dis.h, sim/microblaze, microblaze.h, and
> microblaze.isa.
> * configure.tgt: Add targets microblaze*-linux-*, microblaze*-xilinx-*.
> * doc/gdb.texinfo: Add MicroBlaze.
> * MAINTAINERS: Add self as maintainer for MicroBlaze.
> * Makefile.in: Build microblaze-tdep.o, microblaze-linux-tdep.o.
> HFILES_NO_SRCDIR: Add microblaze-tdep.h.
> * microblaze-linux-tdep.c: New.
> * microblaze-rom.c: New.
> * microblaze-tdep.c: New.
> * microblaze-tdep.h: New.
> * NEWS: Announce Xilinx MicroBlaze support.
Thanks. The changes to fnchange.lst, NEWS and gdb.texinfo are
approved. However, please note that gdb/doc has its own ChangeLog
file, so the entry for gdb.texinfo should go there, not in
gdb/ChangeLog. Also, the entry you put in gdb/doc/ChangeLog should
state the name of the node where you added your text, see the other
entries there for examples.
next prev parent reply other threads:[~2009-10-06 7:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 1:35 Michael Eager
2009-10-06 7:14 ` Eli Zaretskii [this message]
2009-10-14 1:47 ` Joel Brobecker
2009-10-14 17:49 ` Michael Eager
2009-10-14 17:56 ` Daniel Jacobowitz
2009-10-14 18:01 ` Michael Eager
2009-10-15 16:32 Michael Eager
2009-10-15 16:44 ` Tom Tromey
2009-10-15 16:47 ` Joel Brobecker
2009-10-15 18:00 ` Tom Tromey
2009-10-15 18:04 ` Tom Tromey
2009-10-15 18:31 ` Joel Brobecker
2009-10-16 12:53 ` Daniel Jacobowitz
2009-10-16 16:14 ` Michael Eager
2009-10-15 17:12 ` Michael Eager
2009-10-15 17:18 ` Joel Brobecker
2009-10-15 18:06 ` Michael Eager
2009-10-15 16:46 ` Joel Brobecker
2009-10-15 17:14 ` Michael Eager
2009-10-15 19:31 ` Michael Eager
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=83ab05nggh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.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