From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: lgustavo@codesourcery.com
Cc: emachado@linux.vnet.ibm.com (Edjunior Barbosa Machado),
gdb-patches@sourceware.org
Subject: Re: [PATCH] [trivial] Fix test names starting with uppercase in gdb.arch/ppc64-atomic-inst.exp
Date: Wed, 15 Feb 2017 12:59:00 -0000 [thread overview]
Message-ID: <20170215125923.44FDCD83101@oc3748833570.ibm.com> (raw)
In-Reply-To: <50421755-b63b-5068-8e09-366e97cd890d@codesourcery.com> from "Luis Machado" at Feb 15, 2017 03:30:11 AM
Luis Machado wrote:
> On 02/13/2017 09:35 PM, Edjunior Barbosa Machado wrote:
> > Hi,
> > this trivial patch fixes the test names starting with uppercase using gdb_test
> > in gdb.arch/ppc64-atomic-inst.exp.
> >
> > Thanks,
> > --
> > Edjunior
> >
> > gdb/testsuite/
> > 2017-02-14 Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
> >
> > * gdb.arch/ppc64-atomic-inst.exp: Fix test names starting with
> > uppercase.
>
> LGTM.
>
Thanks for the review, Luis! I agree, this patch is OK.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2017-02-15 12:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 3:03 [PATCH] [ppc64] Add POWER8 atomic sequences single-stepping support Edjunior Barbosa Machado
2017-02-06 10:03 ` Luis Machado
2017-02-06 12:55 ` Peter Bergner
2017-02-14 0:48 ` [PATCH v2] " Edjunior Barbosa Machado
2017-02-15 10:00 ` Luis Machado
2017-02-15 12:01 ` Edjunior Barbosa Machado
2017-02-15 12:13 ` Luis Machado
2017-02-16 23:42 ` [PATCH v3] [ppc64] Add POWER8/ISA 2.07 " Edjunior Barbosa Machado
2017-02-20 19:52 ` Luis Machado
2017-02-21 10:55 ` Ulrich Weigand
2017-02-21 14:46 ` Edjunior Barbosa Machado
2017-02-14 3:36 ` [PATCH] [trivial] Fix test names starting with uppercase in gdb.arch/ppc64-atomic-inst.exp Edjunior Barbosa Machado
2017-02-15 9:30 ` Luis Machado
2017-02-15 12:59 ` Ulrich Weigand [this message]
2017-02-21 14:44 ` Edjunior Barbosa 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=20170215125923.44FDCD83101@oc3748833570.ibm.com \
--to=uweigand@de.ibm.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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