From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Theodore Tso <tytso@mit.edu>,
linux-kernel@vger.kernel.org, Amit Arora <aarora@in.ibm.com>,
Andi Kleen <ak@suse.de>, Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Arnd Bergmann <arnd@arndb.de>, "Luck, Tony" <tony.luck@intel.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Mark Fasheh <mark.fasheh@oracle.com>,
linux-arch@vger.kernel.org
Subject: Re: fallocate-implementation-on-i86-x86_64-and-powerpc.patch
Date: Tue, 10 Jul 2007 13:44:32 -0400 [thread overview]
Message-ID: <4693C580.2000506@garzik.org> (raw)
In-Reply-To: <20070710101558.cea7aab1.akpm@linux-foundation.org>
Andrew Morton wrote:
> So I dropped everything. Let's start again from scratch. I'd suggest that
> for now we go with just an i386/x86_64 implementation, let the arch
> maintainers wire things up when that has settled down.
It's my observation that that plan usually works the best. Arch
maintainers come along and wire up batches of syscalls when they have a
chance to glance at the ABI, and catch up with x86[-64].
Jeff
next parent reply other threads:[~2007-07-10 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070710013152.ef2cd200.akpm@linux-foundation.org>
[not found] ` <20070710115251.GG2343@thunk.org>
[not found] ` <20070710101558.cea7aab1.akpm@linux-foundation.org>
2007-07-10 17:44 ` Jeff Garzik [this message]
2007-07-10 23:27 ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Paul Mackerras
2007-07-11 0:16 ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Andrew Morton
2007-07-11 0:50 ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Paul Mackerras
2007-07-11 15:39 ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Theodore Tso
2007-07-11 18:47 ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Heiko Carstens
2007-07-11 20:32 ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Martin Schwidefsky
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=4693C580.2000506@garzik.org \
--to=jeff@garzik.org \
--cc=aarora@in.ibm.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
--cc=tytso@mit.edu \
/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).