From: Paul Mackerras <paulus@samba.org>
To: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Linux process ABI broken in 2.6?
Date: Mon, 12 Dec 2005 13:28:55 +1100 [thread overview]
Message-ID: <17308.57447.992759.27443@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <F6AD7E21CDF4E145A44F61F43EE6D939486E0C@tmnt04.transmode.se>
Joakim Tjernlund writes:
> Is it too much trouble to define r7 to always have
> a zero
> value at process startup?
That's not much trouble, but what will you do for existing kernels?
Won't you have to do something like testing *r1 anyway?
Paul.
next prev parent reply other threads:[~2005-12-12 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 11:05 Linux process ABI broken in 2.6? Joakim Tjernlund
2005-12-12 2:28 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-12 8:09 Joakim Tjernlund
2005-12-11 15:11 Joakim Tjernlund
2005-12-08 23:07 Tjernlund
2005-12-09 2:05 ` Benjamin Herrenschmidt
2005-12-09 3:16 ` Paul Mackerras
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=17308.57447.992759.27443@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linuxppc-dev@ozlabs.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).