All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] High fpu register corruption (PATCH)
Date: Thu, 29 May 2003 04:10:34 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723706066@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705679@msgid-missing>

>>>>> On Wed, 28 May 2003 21:53:13 -0600, Bjorn Helgaas <bjorn_helgaas@hp.com> said:

  Bjorn> I'm comparing 2.4 (including your patch) and David's current
  Bjorn> 2.5 BK tree.  I'd like to keep them as close as possible, but
  Bjorn> I see several clearly gratuitous differences (like
  Bjorn> whitespace) and some that aren't obvious to me.

  Bjorn> arch/ia64/kernel/ptrace.c: 2.4 calls ia64_drop_fpu() from
  Bjorn> ia64_sync_fph().  2.5 calls ia64_drop_fpu() from
  Bjorn> ia64_flush_fph().  Is there a reason for the difference?

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.

	--david


  parent reply	other threads:[~2003-05-29  4:10 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 [this message]
2003-05-29  4:25 ` Bjorn Helgaas
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-105590723706066@msgid-missing \
    --to=davidm@napali.hpl.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 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.