From: Victor Zandy <zandy@cs.wisc.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: Global FPU corruption in 2.2
Date: 24 Apr 2001 14:17:18 -0500 [thread overview]
Message-ID: <cpxoftmqf9d.fsf@goat.cs.wisc.edu> (raw)
In-Reply-To: <E14s7gz-0002fh-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Tue, 24 Apr 2001 19:37:38 +0100 (BST)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> The preferable one for performance is certainly to backport the 2.4 changes
Is it any more substantial than changing all uses of the ptrace flags
to the new variable?
next prev parent reply other threads:[~2001-04-24 19:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 18:21 BUG: Global FPU corruption in 2.2 Victor Zandy
2001-04-24 18:37 ` Alan Cox
2001-04-24 19:17 ` Victor Zandy [this message]
2001-04-24 19:51 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 13:05 Victor Zandy
2001-04-24 16:24 ` Linus Torvalds
2001-04-24 16:47 ` Christian Ehrhardt
2001-04-24 18:09 ` Victor Zandy
2001-04-24 8:56 alad
2001-04-24 7:56 alad
2001-04-24 5:33 alad
2001-04-19 16:05 Victor Zandy
2001-04-19 20:18 ` Michal Jaegermann
2001-04-20 18:50 ` Victor Zandy
2001-04-20 19:07 ` Richard B. Johnson
2001-04-20 19:20 ` Victor Zandy
2001-04-20 19:44 ` Richard B. Johnson
2001-04-20 19:23 ` Ulrich Drepper
2001-04-20 19:37 ` Richard B. Johnson
2001-04-20 20:20 ` Victor Zandy
2001-04-20 21:44 ` Ulrich Drepper
2001-04-22 1:46 ` Richard B. Johnson
2001-04-22 2:18 ` Alan Cox
2001-04-22 2:30 ` Richard B. Johnson
2001-04-22 18:39 ` David Konerding
2001-04-22 18:59 ` Alan Cox
2001-04-22 20:59 ` kees
2001-04-23 16:11 ` Christian Ehrhardt
2001-04-24 16:10 ` Linus Torvalds
2001-04-24 16:25 ` Alan Cox
2001-04-24 16:56 ` Christian Ehrhardt
2001-04-24 20:15 ` Michal Jaegermann
2001-04-23 18:44 ` Erik Paulson
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=cpxoftmqf9d.fsf@goat.cs.wisc.edu \
--to=zandy@cs.wisc.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).