From: Eli Zaretskii <eliz@gnu.org>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH-ppc 5/5] Add VSX doc bits
Date: Fri, 15 Aug 2008 18:22:00 -0000 [thread overview]
Message-ID: <ur68qdttc.fsf@gnu.org> (raw)
In-Reply-To: <1218823977.8946.49.camel@gargoyle>
> From: Luis Machado <luisgpm@linux.vnet.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Fri, 15 Aug 2008 15:12:56 -0300
>
> On Fri, 2008-08-15 at 20:06 +0300, Eli Zaretskii wrote:
> > This needs to state the node name where the changes are made.
>
> > This is OK, modulo Stan's comments on using "new".
>
> Both should be addressed in the patch below.
Yes, but...
> +For POWER7 processors, GDB provides a set of pseudo-registers, the 64-bit
^^^
Literal "GDB". Sorry for not catching this the first time.
next prev parent reply other threads:[~2008-08-15 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 20:16 Luis Machado
2008-08-15 15:29 ` Luis Machado
2008-08-15 15:39 ` Stan Shebs
2008-08-15 15:52 ` Luis Machado
2008-08-15 17:08 ` Eli Zaretskii
2008-08-15 18:14 ` Luis Machado
2008-08-15 18:22 ` Eli Zaretskii [this message]
2008-08-18 16:02 ` Luis Machado
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=ur68qdttc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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