From: Daniel Jacobowitz <dan@debian.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: [PATCH] store sign-extend register values for PTRACE_GETREGS
Date: Sun, 28 Oct 2007 15:52:11 -0400 [thread overview]
Message-ID: <20071028195211.GA29200@caradoc.them.org> (raw)
In-Reply-To: <20071028193421.GC7661@linux-mips.org>
On Sun, Oct 28, 2007 at 07:34:21PM +0000, Ralf Baechle wrote:
> On Fri, Oct 26, 2007 at 12:53:02AM +0900, Atsushi Nemoto wrote:
>
> Daniel, do you see any debugger compatibility issues with this patch?
I don't think so; I'm pretty sure I wrote the code at fault here,
and I can't remember any reason I would have deliberately made the
registers unsigned. Looking at the fix I think I just guessed
wrong about the type used by __put_user.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-28 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 17:41 [PATCH] store sign-extend register values for PTRACE_GETREGS Atsushi Nemoto
2007-10-25 15:53 ` Atsushi Nemoto
2007-10-28 19:34 ` Ralf Baechle
2007-10-28 19:52 ` Daniel Jacobowitz [this message]
2007-10-29 18:31 ` Ralf Baechle
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=20071028195211.GA29200@caradoc.them.org \
--to=dan@debian.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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