From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, Jim Wilson <jim.wilson@linaro.org>,
gdb@sourceware.org
Subject: Re: build bot failure
Date: Wed, 25 May 2016 08:07:00 -0000 [thread overview]
Message-ID: <86k2ii4l2n.fsf@gmail.com> (raw)
In-Reply-To: <f090307c-d2fe-a317-250c-a8e67f2aab9e@redhat.com> (Pedro Alves's message of "Tue, 24 May 2016 17:48:14 +0100")
Pedro Alves <palves@redhat.com> writes:
> Did you try the commit before Jim's? Maybe would helps determine whether
> this is a regression caused by Jim's patch, or some other issue with
> the slave's toolchain.
Build is OK with the commit before Jim's.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-05-25 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 0:40 Jim Wilson
2016-05-24 8:26 ` Yao Qi
2016-05-24 10:39 ` Yao Qi
2016-05-24 16:30 ` Jim Wilson
2016-05-24 16:48 ` Pedro Alves
2016-05-25 8:07 ` Yao Qi [this message]
2016-06-10 16:27 ` Jim Wilson
2016-06-10 18:47 ` Sergio Durigan Junior
2016-06-11 12:26 ` David Edelsohn
2016-06-11 17:00 ` Jim Wilson
2016-06-12 17:27 ` David Edelsohn
2016-06-22 23:15 ` Jim Wilson
2016-06-23 0:57 ` Sergio Durigan Junior
2016-11-14 11:06 ` Yao Qi
2016-11-14 13:01 ` David Edelsohn
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=86k2ii4l2n.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=jim.wilson@linaro.org \
--cc=palves@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