From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: info-shared.exp: Expect leading dot on ppc64's symbols
Date: Wed, 22 Jan 2014 19:42:00 -0000 [thread overview]
Message-ID: <m3mwinvm56.fsf@redhat.com> (raw)
In-Reply-To: <1390418283-11267-1-git-send-email-emachado@linux.vnet.ibm.com> (Edjunior Barbosa Machado's message of "Wed, 22 Jan 2014 17:18:02 -0200")
On Wednesday, January 22 2014, Edjunior Barbosa Machado wrote:
> Hi,
>
> With this patch, the testcase permits the leading `.' found on ppc64's symbols.
> It fixes 10 false unexpected failures on ppc64. Ok?
I believe this also fixes the regressions I found on PPC64 + RHEL 6.5
for the 7.7 branch. I will test the patch and get back with the results.
Thanks,
--
Sergio
next prev parent reply other threads:[~2014-01-22 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 19:18 Edjunior Barbosa Machado
2014-01-22 19:42 ` Sergio Durigan Junior [this message]
2014-01-22 20:52 ` Sergio Durigan Junior
2014-01-28 15:59 ` [PATCH] testsuite: info-shared.exp: Expect leading.on " Ulrich Weigand
2014-01-28 16:36 ` Joel Brobecker
2014-01-28 17:39 ` Edjunior Barbosa Machado
2014-01-28 19:23 ` Sergio Durigan Junior
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=m3mwinvm56.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
/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