Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Lennert Buytenhek <buytenh@gnu.org>,
	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: Mon, 31 Dec 2001 11:29:53 -0200	[thread overview]
Message-ID: <20011231112953.A25924@dea.linux-mips.net> (raw)
In-Reply-To: <je3d1ra60s.fsf@sykes.suse.de>; from schwab@suse.de on Mon, Dec 31, 2001 at 02:11:31PM +0100

On Mon, Dec 31, 2001 at 02:11:31PM +0100, Andreas Schwab wrote:

> |> 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.

While it may break things in userspace it will hopefully ensure correctness
for userspace, so better kill 'em now than later.  _syscallX() has a too
long history of causing problems.

  Ralf

      reply	other threads:[~2001-12-31 16:42 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 ` [Linux-ia64] " Andreas Schwab
2001-12-31 13:29   ` Ralf Baechle [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=20011231112953.A25924@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --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=schwab@suse.de \
    --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