Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Samuel Bronson <naesten@gmail.com>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] ARM Linux support for `catch syscall'
Date: Wed, 07 Aug 2013 15:28:00 -0000	[thread overview]
Message-ID: <CADPb22TUkiyHfATXzeVfB8LzjBOjtu6Ym5gWh3EOHKAX8VfFEA@mail.gmail.com> (raw)
In-Reply-To: <m31u689gic.fsf@redhat.com>

On Mon, Aug 5, 2013 at 10:47 AM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Wednesday, July 31 2013, Samuel Bronson wrote:
>
>> This works alright except for the incomplete syscalls/arm-linux.xml,
>> for which I am waiting on a copy of sergiodj's scripts.
>
> [...]
>
> The rest looks OK to me.  I am not a GDB maintainer, so you may wish to
> wait until someone gives his final word.

Needs a NEWS entry.
With that and sergio's changes I think it's ready.
Thanks!
[Best submit the revised patch to the list for final approval I think.]


  reply	other threads:[~2013-08-07 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 21:04 [RFC][PATCH] Preliminary `catch syscall' support for ARM Linux Samuel Bronson
2013-08-02 16:56 ` Tom Tromey
     [not found] ` <E1V4dYl-0006Y8-79 at hydrogen>
2013-08-02 20:33   ` [PATCH] ARM Linux support for `catch syscall' Samuel Bronson
2013-08-05 17:47     ` Sergio Durigan Junior
2013-08-07 15:28       ` Doug Evans [this message]
     [not found]         ` <E1V9fPE-00060l-WC@hydrogen>
2013-08-14 19:29           ` [PATCH v2] " Sergio Durigan Junior
2013-08-16 18:50             ` Samuel Bronson
2013-08-15 20:05           ` Doug Evans
2013-08-15 20:08             ` Sergio Durigan Junior
2013-08-16 18:53             ` Samuel Bronson

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=CADPb22TUkiyHfATXzeVfB8LzjBOjtu6Ym5gWh3EOHKAX8VfFEA@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=naesten@gmail.com \
    --cc=sergiodj@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