From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro@codesourcery.com (Pedro Alves)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Problems with software single-step and SPU breakpoints during fork
Date: Wed, 23 Jun 2010 13:08:00 -0000 [thread overview]
Message-ID: <201006231307.o5ND7oNR006484@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <201006221715.15713.pedro@codesourcery.com> from "Pedro Alves" at Jun 22, 2010 05:15:15 PM
Pedro Alves wrote:
> On Tuesday 22 June 2010 16:22:37, Ulrich Weigand wrote:
>
> > Below is an updated patch with the changes described above.
> > Tested on powerpc64-linux (on Cell/B.E.).
>
> Looks good to me. Thanks!
Thanks once again for the review!
I've checked the patch in now.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2010-06-23 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 19:30 Ulrich Weigand
2010-06-22 0:49 ` Pedro Alves
2010-06-22 15:22 ` Ulrich Weigand
2010-06-22 16:15 ` Pedro Alves
2010-06-23 13:08 ` Ulrich Weigand [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=201006231307.o5ND7oNR006484@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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