From: george anzinger <george@mvista.com>
To: "David S. Miller" <davem@redhat.com>
Cc: 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 02:35:42 -0700 [thread overview]
Message-ID: <3EB8D36E.10206@mvista.com> (raw)
In-Reply-To: <20030506.195511.74729679.davem@redhat.com>
David S. Miller wrote:
> From: george anzinger <george@mvista.com>
> Date: Tue, 06 May 2003 13:15:05 -0700
>
> David S. Miller wrote:
> > This is not at all how this stuff is supposed to work.
>
> Um, where might one learn how it is _supposed_ to work?
>
> By looking at existing uses.
>
> Some files provide partial APIs, other files are "configured'
> by the asm-ARCH/foo.h header before being included.
>
Yes, I am aware of existing use. Sometimes the asm file just includes
the generic with no additional content. It is these that go away.
This also means that an arch need not supply the asm version UNTIL it
has one that does it better. This might be useful if one wanted to
supply a u64 = u64 * u32 mpy, for example. This can be done in C, but
is rather costly. An arch could supply the asm version at a later
time, but for the short haul, the generic gets them on the air.
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.
As to "_supposed_ to work", I rather though we were making this up as
we went along, as long as we don't change existing usage, and even,
sometimes, that rule is not honored :)
>
--
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 9:24 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 [this message]
2003-05-07 14:30 ` Sam Ravnborg
2003-05-07 15:08 ` george anzinger
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=3EB8D36E.10206@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 \
/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