From: "Andrew Burgess" <aburgess@broadcom.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "Tom Tromey" <tromey@redhat.com>
Subject: Re: [PATCH] gdb.base/code_elim.exp - empty bss issue.
Date: Fri, 30 Aug 2013 16:36:00 -0000 [thread overview]
Message-ID: <5220CA1C.8080608@broadcom.com> (raw)
In-Reply-To: <87y57jm9gj.fsf@fleche.redhat.com>
On 30/08/2013 5:26 PM, Tom Tromey wrote:
>>>>>> "Andrew" == Andrew Burgess <aburgess@broadcom.com> writes:
>
> Andrew> 2013-08-30 Andrew Burgess <aburgess@broadcom.com>
> Andrew> * gdb.base/code_elim1.c (my_bss_symbol): New variable added.
> Andrew> (my_static_symbol): Add comment.
> Andrew> (main): Reference my_bss_symbol.
>
> Ok.
Committed. Thanks for the quick review.
Andrew
prev parent reply other threads:[~2013-08-30 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 15:11 Andrew Burgess
2013-08-30 16:26 ` Tom Tromey
2013-08-30 16:36 ` Andrew Burgess [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=5220CA1C.8080608@broadcom.com \
--to=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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