public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: davidm@HPL.HP.COM, torvalds@osdl.org, jes@wildopensource.com,
	hch@infradead.org, linux-kernel@vger.kernel.org,
	jun.nakajima@intel.com, asit.k.mallick@intel.com
Subject: Re: [Patch] asm workarounds in generic header files
Date: Tue, 9 Sep 2003 22:08:08 -0700	[thread overview]
Message-ID: <20030909220808.31eb29ca.akpm@osdl.org> (raw)
In-Reply-To: <A609E6D693908E4697BF8BB87E76A07A022114C1@fmsmsx408.fm.intel.com>

"Siddha, Suresh B" <suresh.b.siddha@intel.com> wrote:
>
> --- linux/include/linux/compiler-intel.h	Wed Dec 31 16:00:00 1969
>  +++ linux-/include/linux/compiler-intel.h	Tue Sep  9 21:34:19 2003
>  @@ -0,0 +1,21 @@
>  +/* Never include this file directly.  Include <linux/compiler.h> instead.  */
>  +
>  +#ifdef __ECC
>  +
>  +/* Some compiler specific definitions are overwritten here
>  + * for Intel ECC compiler 
>  + */
>  +
>  +#include <asm/intrinsics.h>

This is ia64-only, yes?

Where do we stand with ECC/ia32 support?


  reply	other threads:[~2003-09-10  5:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10  4:50 [Patch] asm workarounds in generic header files Siddha, Suresh B
2003-09-10  5:08 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-10  5:51 Nakajima, Jun
2003-09-09 19:34 Siddha, Suresh B
2003-09-09 19:51 ` Jes Sorensen
2003-09-09 20:25   ` David Mosberger
2003-09-09 20:33     ` Linus Torvalds
2003-09-09 21:16       ` Sam Ravnborg
2003-09-09 23:44       ` David Mosberger
2003-09-10 16:22     ` Jes Sorensen
2003-09-10 17:02       ` David Mosberger
2003-09-09  1:04 Siddha, Suresh B
2003-09-09  2:27 ` Jes Sorensen
2003-09-09  6:40 ` Christoph Hellwig

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=20030909220808.31eb29ca.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=asit.k.mallick@intel.com \
    --cc=davidm@HPL.HP.COM \
    --cc=hch@infradead.org \
    --cc=jes@wildopensource.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@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