From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: palves@redhat.com (Pedro Alves), gdb-patches@sourceware.org
Subject: Re: [rfc v4][0/6] Remote /proc file access (Re: [rfc v3][0/6] Remote /proc file access)
Date: Fri, 20 Jan 2012 10:02:00 -0000 [thread overview]
Message-ID: <201201201001.q0KA10VP013686@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20120120055520.GK31383@adacore.com> from "Joel Brobecker" at Jan 20, 2012 09:55:20 AM
Joel Brobecker wrote:
> > I tested the patch series on mips-irix again, and I am happy to
> > report that there are no regression. I haven't had time to
> > test on sparc-solaris today, and I probably won't, but I will
> > give it a shot tomorrow if I can (it's more difficult because
> > I need to use another baseline and your patches do not apply
> > cleanly).
>
> And I confirm no regression on sparc-solaris either using AdaCore's
> testsuite. The goal of testing on sparc-solaris was to perform some
> thread-specific testing, JIC, even if it's only with our testsuite.
Thanks again for your support!
I've now checked in the full patch series.
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:[~2012-01-20 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:41 [rfc v3][0/6] Remote /proc file access Ulrich Weigand
2012-01-17 20:19 ` Pedro Alves
2012-01-17 20:33 ` Ulrich Weigand
2012-01-18 11:46 ` Joel Brobecker
2012-01-18 12:09 ` Pedro Alves
2012-01-18 15:33 ` Ulrich Weigand
2012-01-19 10:00 ` Joel Brobecker
2012-01-19 10:01 ` [rfc v4][0/6] Remote /proc file access (Re: [rfc v3][0/6] Remote /proc file access) Ulrich Weigand
2012-01-19 16:03 ` Joel Brobecker
2012-01-20 10:01 ` Joel Brobecker
2012-01-20 10:02 ` 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=201201201001.q0KA10VP013686@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.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