All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Carsten Langgaard <carstenl@mips.com>,
	"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Bug in __copy_user
Date: Mon, 24 Jun 2002 20:05:04 +0400	[thread overview]
Message-ID: <3D174330.BAEBC56@niisi.msk.ru> (raw)
In-Reply-To: 20020624173954.A1109@dea.linux-mips.net

Ralf Baechle wrote:
> 
> Gleb,
> 
> On Mon, Jun 24, 2002 at 07:14:51PM +0400, Gleb O. Raiko wrote:
> 
> > This patch also solves the problem for mips in 2.4/2.5 kernel. My
> > question was about the patch for mips64 and mips in 2.2 kernel.
> >
> > Shall memcpy.S from 2.4/2.5 be backported to 2.2 and mips64?
> 
> I think that would be the prefered solution as it'll be easier to maintain.
> 
> I've not received any 2.2 patches in a very long, long time - anybody
> actually still using it?

Yes, I am still using 2.2. Considering pathes, I've got patches for r3k,
which doesn't work with a standard 2.2 kernel. But those patches are
backports from 2.4. So, I don't think they shall be applied. From other
hand, I don't plan develop 'normal' patches for 2.2.

Regards,
Gleb.

  reply	other threads:[~2002-06-24 16:00 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 [this message]
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

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=3D174330.BAEBC56@niisi.msk.ru \
    --to=raiko@niisi.msk.ru \
    --cc=carstenl@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.