From: Mark Kettenis <kettenis@chello.nl>
To: jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: handle missing fpregs
Date: Fri, 07 May 2004 11:20:00 -0000 [thread overview]
Message-ID: <200405071120.i47BK7BB007127@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <vt21xlx19f8.fsf@zenia.home> (message from Jim Blandy on 06 May 2004 17:24:11 -0500)
From: Jim Blandy <jimb@redhat.com>
Date: 06 May 2004 17:24:11 -0500
This certainly looks good to me. One nit though. It seems you forgot
about a ChangeLog entry for the changes to
rs6000-tdep.c:ppc_supply_fpregset() and friends.
Mark
next prev parent reply other threads:[~2004-05-07 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 1:19 Jim Blandy
2004-05-07 11:20 ` Mark Kettenis [this message]
2004-05-07 20:54 ` Jim Blandy
2004-05-07 20:18 ` Kevin Buettner
2004-05-07 21:09 ` Jim Blandy
2004-05-07 22:56 ` Kevin Buettner
2004-05-10 17:08 ` Jim Blandy
2004-05-10 19:00 ` Jim Blandy
[not found] ` <D567851C-A2B8-11D8-94E3-000A957650EC@wasabisystems.com>
2004-05-10 22:16 ` Jim Blandy
2004-05-10 22:28 ` Jason Thorpe
2004-05-11 4:55 ` Jim Blandy
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=200405071120.i47BK7BB007127@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.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