From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [rfc] Define PTRACE_GETSIGINFO in linux-nat.c
Date: Tue, 02 Oct 2007 11:41:00 -0000 [thread overview]
Message-ID: <20071002114058.GA11354@caradoc.them.org> (raw)
In-Reply-To: <4701EC60.70702@de.ibm.com>
On Tue, Oct 02, 2007 at 08:59:44AM +0200, Markus Deuling wrote:
> ChangeLog:
>
> * linux-nat.c (PTRACE_GETSIGINFO): Add define.
>
> Tested on x86.
I'm really sorry. Two people told me about this and I still forgot to
fix it before I committed. Patch is OK.
> Is this ok to commit or would it be better to move it to a header (linux-nat.h
> ?) file and delete it from ppc-linux-nat.c as well to prevent redundancy?
ppc-linux-nat.c doesn't need it any more; you can just delete that
copy. I removed the use.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-02 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 7:01 Markus Deuling
2007-10-02 11:41 ` Daniel Jacobowitz [this message]
2007-10-02 16:34 ` 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=20071002114058.GA11354@caradoc.them.org \
--to=drow@false.org \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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