From: Andreas Schwab <schwab@suse.de>
To: Lennert Buytenhek <buytenh@gnu.org>
Cc: rth@dot.cygnus.com, linux-arm-kernel@lists.arm.linux.org.uk,
dev-etrax@axis.com, linux-ia64@linuxia64.org,
linux-m68k@lists.linux-m68k.org, linux-mips@oss.sgi.com,
grundler@cup.hp.com, cort@fsmlabs.com, linux-390@vm.marist.edu,
gniibe@mri.co.jp, sparclinux@vger.kernel.org,
ultralinux@vger.kernel.org, jdike@karaya.com
Subject: Re: [Linux-ia64] [PATCH][RFC][CFT] remove global errno from the kernel, make _syscallX kernel-only
Date: 31 Dec 2001 14:11:31 +0100 [thread overview]
Message-ID: <je3d1ra60s.fsf@sykes.suse.de> (raw)
In-Reply-To: <20011230220500.A10224@gnu.org> (Lennert Buytenhek's message of "Sun, 30 Dec 2001 22:05:00 -0500")
Lennert Buytenhek <buytenh@gnu.org> writes:
|> What I would like to know from each architecture team:
|> - What is your arch's policy on userspace usage of asm/unistd.h, and
|> consequently, what is your opinion on the goal these patches
|> aim for?
I very much appreciate the removal of the _syscallX macros. FWIW, the
ia64 version of these macros never worked in userspace anyway.
|> - Are the changes I made in [1] and [2] for your $arch technically
|> correct?
The m68k changes look ok.
|> Please CC me on replies as I'm not on any of the lists posted to.
|>
|> My intention is to push these to Linus for 2.5 if everyone agrees.
|> They're probably too intrusive for 2.4 (although I'd love people
|> to convince me otherwise).
I wouldn't mind putting it into 2.4.
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-12-31 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 3:05 [PATCH][RFC][CFT] remove global errno from the kernel, make _syscallX kernel-only Lennert Buytenhek
2001-12-31 13:11 ` Andreas Schwab [this message]
2001-12-31 13:29 ` [Linux-ia64] " 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=je3d1ra60s.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=buytenh@gnu.org \
--cc=cort@fsmlabs.com \
--cc=dev-etrax@axis.com \
--cc=gniibe@mri.co.jp \
--cc=grundler@cup.hp.com \
--cc=jdike@karaya.com \
--cc=linux-390@vm.marist.edu \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-ia64@linuxia64.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@oss.sgi.com \
--cc=rth@dot.cygnus.com \
--cc=sparclinux@vger.kernel.org \
--cc=ultralinux@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