Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "M. R. Brown" <mrbrown@0xd6.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	"Gleb O. Raiko" <raiko@niisi.msk.ru>,
	Carsten Langgaard <carstenl@mips.com>,
	linux-mips@oss.sgi.com
Subject: Re: Bug in __copy_user
Date: Mon, 24 Jun 2002 14:49:22 -0500	[thread overview]
Message-ID: <20020624194922.GB12960@0xd6.org> (raw)
In-Reply-To: <004101c21b9d$a2181d60$10eca8c0@grendel>

[-- Attachment #1: Type: text/plain, Size: 703 bytes --]

* Kevin D. Kissell <kevink@mips.com> on Mon, Jun 24, 2002:

> From: "Ralf Baechle" <ralf@oss.sgi.com>
> > On Mon, Jun 24, 2002 at 06:07:18PM +0200, Kevin D. Kissell wrote:
> > 
> > > Only a few thousand (or tens of thousands) of Sony Playstation 2
> > > users.  ;-)  Most of them are running the wierd 2.2.1.?? Sony
> > > branch, but there are a few poor deluded souls tryng to update
> > > to 2.2.20...
> > 
> > Just in time when the Linux world has already mostly abandoned 2.2 ...
> 
> Well, like I said last week, we need to get the PS2 onto 2.4 ASAP,
> for a whole bunch of reasons...
> 

ps2hacking.sourceforge.net - broken port of Sony's 2.2.1 kernel to 2.4.8
(or so).

M. R.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2002-06-24 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 14:17 Bug in __copy_user Carsten Langgaard
2002-06-24 15:14 ` Gleb O. Raiko
2002-06-24 15:39   ` Ralf Baechle
2002-06-24 16:05     ` Gleb O. Raiko
2002-06-24 16:07     ` Kevin D. Kissell
2002-06-24 16:07       ` Kevin D. Kissell
2002-06-24 16:22       ` Ralf Baechle
2002-06-24 16:38         ` Kevin D. Kissell
2002-06-24 16:38           ` Kevin D. Kissell
2002-06-24 19:49           ` M. R. Brown [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=20020624194922.GB12960@0xd6.org \
    --to=mrbrown@0xd6.org \
    --cc=carstenl@mips.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=raiko@niisi.msk.ru \
    --cc=ralf@oss.sgi.com \
    /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