From: "Andrew Burgess" <aburgess@broadcom.com>
To: gdb-patches@sourceware.org
Cc: "Pedro Alves" <palves@redhat.com>
Subject: Re: PING: Re: [PATCH] Print <unavailable> for unavailable registers
Date: Tue, 29 Oct 2013 13:37:00 -0000 [thread overview]
Message-ID: <526FBA25.1050403@broadcom.com> (raw)
In-Reply-To: <5269788C.4050607@redhat.com>
On 24/10/2013 8:44 PM, Pedro Alves wrote:
> On 10/16/2013 03:26 PM, Andrew Burgess wrote:
>> Is this OK to apply?
>
> OK.
>
I've pushed this patch now, sorry for the delay.
First commit to the new git repo so I hope I got it all right.
Thanks,
Andrew
prev parent reply other threads:[~2013-10-29 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 13:09 Andrew Burgess
2013-08-28 15:26 ` PING: " Andrew Burgess
2013-09-18 14:48 ` PING: " Andrew Burgess
2013-09-18 16:06 ` Pedro Alves
2013-10-16 14:26 ` Andrew Burgess
2013-10-24 19:44 ` Pedro Alves
2013-10-29 13:37 ` 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=526FBA25.1050403@broadcom.com \
--to=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.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