From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Kamble, Nitin A" <nitin.a.kamble@intel.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, "Nakajima,
Jun" <jun.nakajima@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: Re: [PATCH] mxcsr patch for i386 & x86-64
Date: Tue, 04 May 2004 17:07:44 -0400 [thread overview]
Message-ID: <40980620.1040405@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0405041322570.3271@ppc970.osdl.org>
Linus Torvalds wrote:
> --- 1.19/arch/i386/kernel/i387.c Tue Feb 3 21:30:39 2004
> +++ edited/arch/i386/kernel/i387.c Tue May 4 13:15:10 2004
> @@ -24,6 +25,21 @@
> #define HAVE_HWFP 1
> #endif
>
> +static unsigned long mxcsr_feature_mask = 0xffffffff;
> --- 1.10/arch/x86_64/kernel/i387.c Fri Jan 23 12:17:58 2004
> +++ edited/arch/x86_64/kernel/i387.c Tue May 4 13:07:35 2004
> @@ -24,6 +24,18 @@
> #include <asm/ptrace.h>
> #include <asm/uaccess.h>
>
> +unsigned long mxcsr_feature_mask = 0xffffffff;
> +
Minor/dumb question: Is the above intentional?
Would be nice to have them the same for consistency if nothing else.
i386 and x86-64 common code gets pasted and #include'd all the time.
Jeff
next prev parent reply other threads:[~2004-05-04 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 18:50 [PATCH] mxcsr patch for i386 & x86-64 Kamble, Nitin A
2004-05-04 19:10 ` Linus Torvalds
2004-05-04 19:26 ` Linus Torvalds
2004-05-04 20:24 ` Linus Torvalds
2004-05-04 21:07 ` Jeff Garzik [this message]
2004-05-05 13:51 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-05-04 20:25 Kamble, Nitin A
2004-05-04 21:06 Kamble, Nitin A
2004-05-04 21:47 Nakajima, Jun
2004-05-06 21:00 Kamble, Nitin A
2004-05-07 14:23 ` Pavel Machek
2004-05-07 1:40 Kamble, Nitin A
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=40980620.1040405@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=asit.k.mallick@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nitin.a.kamble@intel.com \
--cc=sunil.saxena@intel.com \
--cc=torvalds@osdl.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