From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] High fpu register corruption (PATCH)
Date: Thu, 29 May 2003 04:25:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723706067@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705679@msgid-missing>
> Which tree are you looking at? to-linus-2.5 or linux-ia64-2.5? I have
> gotten quite lazy in pushing the former, since the only reason now to
> do a push there is when I want Linus to do a pull. The latter tree is
> much more active.
The latter (linux-ia64-2.5). But ... argh! I've been doing "bk changes -R"
to watch for your updates, and saw none. BUT, I just did a "bk pull"
and got a lot of them.
OK, ignore my questions about ptrace.c and setup.c. Questions still
open:
arch/ia64/kernel/signal.c:
restore_sigcontext() changes look equivalent, but have
gratuitous differences from 2.5 (reversed sense of test,
comment)
arch/ia64/kernel/traps.c:
Gratuitous whitespace differences.
include/asm-ia64/processor.h:
ia64_is_local_fpu_owner(), ia64_set_local_fpu_owner():
these look functionally equivalent in 2.4 and 2.5.
Can they be made identical?
include/asm-ia64/system.h:
IA64_HAS_EXTRA_STATE() and switch_to() appear to be
identical in 2.4 and 2.5 except for whitespace changes.
Can they be made identical?
Bjorn
next prev parent reply other threads:[~2003-05-29 4:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 14:16 [Linux-ia64] High fpu register corruption Andreas Schwab
2003-05-08 16:33 ` Mallick, Asit K
2003-05-08 16:42 ` Chris Mason
2003-05-08 16:58 ` David Mosberger
2003-05-08 17:03 ` David Mosberger
2003-05-08 17:14 ` Mallick, Asit K
2003-05-08 17:55 ` David Mosberger
2003-05-22 21:55 ` [Linux-ia64] High fpu register corruption (PATCH) Mallick, Asit K
2003-05-29 3:53 ` Bjorn Helgaas
2003-05-29 4:10 ` David Mosberger
2003-05-29 4:25 ` Bjorn Helgaas [this message]
2003-05-29 4:40 ` David Mosberger
2003-05-29 5:43 ` Mallick, Asit K
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=marc-linux-ia64-105590723706067@msgid-missing \
--to=bjorn_helgaas@hp.com \
--cc=linux-ia64@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