From: Ulrich Weigand <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com, brobecker@adacore.com
Subject: [rfc v3][0/6] Remote /proc file access
Date: Tue, 17 Jan 2012 19:41:00 -0000 [thread overview]
Message-ID: <OF5DB6AADD.80E0AB5F-ONC1257988.006C1C48@de.ibm.com> (raw)
Hello,
this implements the suggestions I received as feedback from
the v2 version of the patch series.
I've tested this series on i386 native and remote, as well as
on ARM remotely; no change to the previous version.
Joel, would you mind re-running the tests on a procfs target
since this patch does change the procfs.c file, which I cannot
test ... Thanks!
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2012-01-17 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:41 Ulrich Weigand [this message]
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
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=OF5DB6AADD.80E0AB5F-ONC1257988.006C1C48@de.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