From: Blaisorblade <blaisorblade@yahoo.it>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Laurent Vivier <LaurentVivier@wanadoo.fr>,
linux-kernel@vger.kernel.org, Jeff Dike <jdike@addtoit.com>,
"Paolo 'Blaisorblade' Giarrusso" <blaisorblade_spam@yahoo.it>,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: PTRACE_SYSEMU numbering
Date: Thu, 6 Oct 2005 21:23:30 +0200 [thread overview]
Message-ID: <200510062123.31525.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050923151017.GA2558@nevyn.them.org>
On Friday 23 September 2005 17:10, Daniel Jacobowitz wrote:
> On Thu, Sep 22, 2005 at 09:46:38PM +0200, Blaisorblade wrote:
> > The fix is easy, IMHO, and not even urgent. It suffices to move
> > PTRACE_SYSEMU def from <linux/ptrace.h> to <asm-i386/ptrace.h>, and we
> > didn't do that yet for laziness only. There's no architecture that I know
> > of, apart i386, which implements SYSEMU (except maybe s390, but that
> > isn't public).
> Please either renumber it to something above 0x4200,
> or make it i386
> private.
I'm going to do this.
> If you intend for other architectures to implement it in the
> future, renumbering it would be better.
Possibly yes, sooner or later ports will emerge, but this is already in
production, so I have ABI issues.
For new archs, I'll use the right range.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
prev parent reply other threads:[~2005-10-06 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 17:25 PTRACE_SYSEMU numbering Daniel Jacobowitz
2005-09-22 6:48 ` Laurent Vivier
2005-09-22 19:46 ` Blaisorblade
2005-09-23 15:10 ` Daniel Jacobowitz
2005-10-06 19:23 ` Blaisorblade [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=200510062123.31525.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=LaurentVivier@wanadoo.fr \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=dan@debian.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).