From: "David S. Miller" <davem@redhat.com>
To: george@mvista.com
Cc: sam@ravnborg.org, 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 07:06:46 -0700 (PDT) [thread overview]
Message-ID: <20030507.070646.54208027.davem@redhat.com> (raw)
In-Reply-To: <3EB92176.8010803@mvista.com>
From: george anzinger <george@mvista.com>
Date: Wed, 07 May 2003 08:08:38 -0700
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.
This is desirable behavior, then the arch maintainer sees the breakage
and if the asm-generic solution is appropriate he makes that
decision.
I don't think you want to play expert for port maintainers.
I sense that you want to be able to do "instant ports" to
some architecture. This isn't the way to do it. Instead
tar up a template set of asm-foo/ header files, and dump that
into the directory for your new port.
I see absolutely no value whatsoever to what you are proposing.
In fact, I frankly think it sucks. :(
next prev parent reply other threads:[~2003-05-07 15:02 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
2003-05-07 14:06 ` David S. Miller [this message]
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=20030507.070646.54208027.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@zip.com.au \
--cc=george@mvista.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