From: Mark Kettenis <kettenis@wins.uva.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH]: i387-nat.h doc fix
Date: Sat, 17 Mar 2001 15:01:00 -0000 [thread overview]
Message-ID: <200103172301.f2HN1Hl09641@delius.kettenis.local> (raw)
This makes the comment match the prototype.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* i387-nat.h: Doc Fix.
Index: i387-nat.h
===================================================================
RCS file: /cvs/src/src/gdb/i387-nat.h,v
retrieving revision 1.3
diff -u -p -r1.3 i387-nat.h
--- i387-nat.h 2001/02/17 09:01:14 1.3
+++ i387-nat.h 2001/03/17 22:37:27
@@ -21,7 +21,7 @@
#ifndef I387_NAT_H
#define I387_NAT_H
-/* Fill register REGNO in GDB's register array with the appropriate
+/* Fill register REGNUM in GDB's register array with the appropriate
value from *FSAVE. This function masks off any of the reserved
bits in *FSAVE. */
reply other threads:[~2001-03-17 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200103172301.f2HN1Hl09641@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=gdb-patches@sources.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