From: Ralf Baechle <ralf@oss.sgi.com>
To: "Gleb O. Raiko" <raiko@niisi.msk.ru>
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 17:39:55 +0200 [thread overview]
Message-ID: <20020624173954.A1109@dea.linux-mips.net> (raw)
In-Reply-To: <3D17376B.59333E27@niisi.msk.ru>; from raiko@niisi.msk.ru on Mon, Jun 24, 2002 at 07:14:51PM +0400
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?
Ralf
next prev parent reply other threads:[~2002-06-24 15:40 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 [this message]
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
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=20020624173954.A1109@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=carstenl@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=raiko@niisi.msk.ru \
/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