From: "David S. Miller" <davem@redhat.com>
To: george@mvista.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: Tue, 06 May 2003 19:55:11 -0700 (PDT) [thread overview]
Message-ID: <20030506.195511.74729679.davem@redhat.com> (raw)
In-Reply-To: <3EB817C9.8020603@mvista.com>
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.
next prev parent reply other threads:[~2003-05-07 3:50 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 [this message]
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
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=20030506.195511.74729679.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 \
/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;
as well as URLs for NNTP newsgroup(s).