From: Tamar Christina <Tamar.Christina@arm.com>
To: Tom Tromey <tom@tromey.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
"keiths@redhat.com" <keiths@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: RE: [RFA 2/3] PR gdb/20653 - small cleanup in string_to_explicit_location
Date: Thu, 06 Oct 2016 15:42:00 -0000 [thread overview]
Message-ID: <VI1PR0801MB2031F525CE3958382EA2F660FFC70@VI1PR0801MB2031.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <87mvihecf9.fsf@tromey.com>
> -----Original Message-----
> From: Tom Tromey [mailto:tom@tromey.com]
> Sent: 06 October 2016 16:16
> To: Tamar Christina
> Cc: tom@tromey.com; Yao Qi; keiths@redhat.com; gdb-
> patches@sourceware.org; nd
> Subject: Re: [RFA 2/3] PR gdb/20653 - small cleanup in
> string_to_explicit_location
>
> >>>>> "Tamar" == Tamar Christina <Tamar.Christina@arm.com> writes:
>
> Tamar> Any progress on getting this patch committed?
> Tamar> This issue is currently breaking our nightlies.
>
> I pushed the patch yesterday.
Ah, great. Thanks, I see it in the queue for build tonight.
> Did it cause some problem? And if so, what?
>
No, the patch did not cause a problem. I have been waiting for the patch to
solve a problem. Without the patch compilation fails as we compile with
Warnings as errors.
Thanks,
Tamar
next prev parent reply other threads:[~2016-10-06 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR0801MB2031F8BBE482E30DC339C2E1FFC70@VI1PR0801MB2031.eurprd08.prod.outlook.com>
2016-10-06 9:10 ` Tamar Christina
2016-10-06 15:36 ` Tom Tromey
2016-10-06 15:42 ` Tamar Christina [this message]
[not found] ` <CAH=s-PNRhbe9pypkm4=VwCo_Y+CNwcW1PCjC=vBeb2Us7tUHWQ@mail.gmail.com>
2016-10-24 11:10 ` Yao Qi
2016-10-03 21:54 [RFA 0/3] Fix various bugs found by static analysis Tom Tromey
2016-10-03 21:54 ` [RFA 2/3] PR gdb/20653 - small cleanup in string_to_explicit_location Tom Tromey
2016-10-03 22:27 ` Keith Seitz
2016-10-04 10:50 ` Yao Qi
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=VI1PR0801MB2031F525CE3958382EA2F660FFC70@VI1PR0801MB2031.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=nd@arm.com \
--cc=qiyaoltc@gmail.com \
--cc=tom@tromey.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