From: george anzinger <george@mvista.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "David S. Miller" <davem@redhat.com>,
akpm@zip.com.au, kbuild-devel@lists.sourceforge.net,
mec@shout.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asm-generic magic
Date: Wed, 07 May 2003 08:08:38 -0700 [thread overview]
Message-ID: <3EB92176.8010803@mvista.com> (raw)
In-Reply-To: <20030507143059.GA1057@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Wed, May 07, 2003 at 02:35:42AM -0700, george anzinger wrote:
>
>>If the arch wanted to supply only some of the content, the configure
>>option as is used with some today, is still available. CURRENT USAGE
>>IS NOT AFFECTED.
>
>
> The usage of magic symlinks shall be kept minimal.
> The asm -> $(ARCH)-asm symlink already has caused me troubles when
> doing cross compilation. Also the separate obj tree patch treats
> the symlink with special care.
>
> the gain should be high introducing one more symlink.
> For what I understood the gain is only to avoid a couple of
> one line files that include another file. Not enough to justify a
> second symlink IMHO.
That is a good point. To the other side, the symlink is arch
independent and is just "asm->." Also, if you are introducing a file
with asm code, you either cause all "other" archs to fail (till they
catch up) or you must introduce the simple one line file in each arch.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-05-07 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 6:41 [PATCH] asm-generic magic george anzinger
2003-05-06 7:26 ` David S. Miller
2003-05-06 20:15 ` george anzinger
2003-05-07 2:55 ` David S. Miller
2003-05-07 9:35 ` george anzinger
2003-05-07 14:30 ` Sam Ravnborg
2003-05-07 15:08 ` george anzinger [this message]
2003-05-07 14:06 ` David S. Miller
2003-05-07 15:33 ` george anzinger
2003-05-07 14:31 ` David S. Miller
2003-05-07 15:24 ` Kbuild newbie/promotional docs needed John van V.
2003-05-07 20:24 ` Sam Ravnborg
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=3EB92176.8010803@mvista.com \
--to=george@mvista.com \
--cc=akpm@zip.com.au \
--cc=davem@redhat.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=sam@ravnborg.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