From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: davidm@hpl.hp.com, Jes Sorensen <jes@wildopensource.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, "Nakajima,
Jun" <jun.nakajima@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>
Subject: Re: [Patch] asm workarounds in generic header files
Date: Tue, 9 Sep 2003 23:16:36 +0200 [thread overview]
Message-ID: <20030909211636.GA4400@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0309091329570.30594-100000@home.osdl.org>
On Tue, Sep 09, 2003 at 01:33:51PM -0700, Linus Torvalds wrote:
>
> Then, have a config-time "set the right symbolic link" the same way we do
> for "include/asm/", so that we can have a set of _clean_
> compiler-dependent abstractions.
I would prefer to have a compiler.h like this:
#if COMPILER=GCC-2.95
#include <compiler_gcc295.h
#endif
#if COMPILER=INTEL
#include <compiler_intel.h>
#endif
Better one more indirection in a simple compiler.h file than another symlink.
Symlinks should be used in rare cases only.
Sam
next prev parent reply other threads:[~2003-09-09 21:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 19:34 [Patch] asm workarounds in generic header files 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 [this message]
2003-09-09 23:44 ` David Mosberger
2003-09-10 16:22 ` Jes Sorensen
2003-09-10 17:02 ` David Mosberger
-- strict thread matches above, loose matches on Subject: below --
2003-09-10 5:51 Nakajima, Jun
2003-09-10 4:50 Siddha, Suresh B
2003-09-10 5:08 ` Andrew Morton
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=20030909211636.GA4400@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=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