From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [PowerPC] Aliases for vector registers
Date: Mon, 14 Jan 2019 19:36:00 -0000 [thread overview]
Message-ID: <87y37nghhm.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190114140313.52BA9D8033F@oc3748833570.ibm.com>
Ulrich Weigand <uweigand@de.ibm.com> writes:
> This is OK.
>
> Thanks,
> Ulrich
>
> --
> Dr. Ulrich Weigand
> GNU/Linux compilers and toolchain
> Ulrich.Weigand@de.ibm.com
Thanks for the review, I've checked these in.
--
Pedro Franco de Carvalho
prev parent reply other threads:[~2019-01-14 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 19:49 Pedro Franco de Carvalho
2019-01-10 19:45 ` [PATCH] [PowerPC] Fix "info vector" test in gdb.arch/altivec-regs.exp Pedro Franco de Carvalho
2019-01-14 14:02 ` Ulrich Weigand
2019-01-14 14:17 ` Andreas Schwab
2019-01-14 19:36 ` Pedro Franco de Carvalho
2019-01-11 6:59 ` [PATCH] [PowerPC] Aliases for vector registers Eli Zaretskii
2019-01-11 18:01 ` Pedro Franco de Carvalho
2019-01-14 14:03 ` Ulrich Weigand
2019-01-14 19:36 ` Pedro Franco de Carvalho [this message]
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=87y37nghhm.fsf@linux.vnet.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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