From: Pedro Alves <palves@redhat.com>
To: Yufeng Zhang <Yufeng.Zhang@arm.com>
Cc: Marcus Shawcroft <marcus.shawcroft@gmail.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [native AAarch64 GNU/Linux] Access debug register mirror from the corresponding process.
Date: Wed, 13 Feb 2013 19:04:00 -0000 [thread overview]
Message-ID: <511BE39D.3010006@redhat.com> (raw)
In-Reply-To: <511BE1EF.3020408@arm.com>
On 02/13/2013 06:56 PM, Yufeng Zhang wrote:
> On 02/13/13 16:01, Pedro Alves wrote:
>> On 02/13/2013 03:21 PM, Marcus Shawcroft wrote:
>>>> I'll send you an aarch64 version of this patch, unless you've
>>>> already started porting the necessary bits over.
>>>
>>> We were just about to get started... but if you have a patch in hand
>>> that would be great!
>>
>> Here it is. Completely untested, of course. But hopefully not
>> too far off.
>
> Not far off at all; thanks! I have tested your patch and made some further changes; please find the attached patch. The two patches together seem to be working.
Those changes look fine. Please merge them, and go ahead
post/commit the resulting patch.
--
Pedro Alves
next prev parent reply other threads:[~2013-02-13 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:33 [PATCH] [native x86 GNU/Linux] Access debug register mirror from the corresponding inferior Pedro Alves
2013-02-07 16:59 ` Jan Kratochvil
2013-02-11 21:10 ` Pedro Alves
2013-02-12 12:36 ` Pedro Alves
2013-02-12 16:50 ` Jan Kratochvil
2013-02-13 15:04 ` Pedro Alves
2013-02-13 14:20 ` Yufeng Zhang
2013-02-13 14:51 ` Pedro Alves
2013-02-13 15:14 ` Pedro Alves
2013-02-13 15:21 ` Marcus Shawcroft
2013-02-13 16:02 ` [native AAarch64 GNU/Linux] Access debug register mirror from the corresponding process Pedro Alves
2013-02-13 18:57 ` Yufeng Zhang
2013-02-13 19:04 ` Pedro Alves [this message]
2013-02-14 10:13 ` Yufeng Zhang
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=511BE39D.3010006@redhat.com \
--to=palves@redhat.com \
--cc=Yufeng.Zhang@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=marcus.shawcroft@gmail.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