From: Al Viro <viro@ftp.linux.org.uk>
To: Paul Mackerras <paulus@samba.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Arnd Bergmann <arnd@arndb.de>,
linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org,
arjan@infradead.org
Subject: Re: [PATCH 02/14] spufs: fix local store page refcounting
Date: Wed, 7 Dec 2005 10:17:08 +0000 [thread overview]
Message-ID: <20051207101708.GJ27946@ftp.linux.org.uk> (raw)
In-Reply-To: <17302.21437.608048.64857@cargo.ozlabs.ibm.com>
On Wed, Dec 07, 2005 at 02:15:09PM +1100, Paul Mackerras wrote:
> Al Viro writes:
>
> > FWIW, I think it's not a serious argument. Interface changes => grep time.
> > And that means grep over the tree anyway.
>
> OK, well, where would you prefer the spufs code to go?
Up to ppc folks, really - I don't see any serious objections to arch/powerpc/
variants; it could go there, it could go to fs/*. Objections along the lines
of "it won't be found" are BS - any interface change is going to start with
grep over the entire tree anyway.
> > That's solved by asking for review...
>
> Could you review the spufs code (i.e. the patches posted by Arnd
> recently to linuxppc64-dev@ozlabs.org) please?
If it's what you have in powerpc.git - see comments on IRC yesterday...
next prev parent reply other threads:[~2005-12-07 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051206035220.097737000@localhost>
[not found] ` <200512061118.19633.arnd@arndb.de>
[not found] ` <1133869108.7968.1.camel@localhost>
2005-12-06 18:49 ` [PATCH 02/14] spufs: fix local store page refcounting Arnd Bergmann
2005-12-06 19:05 ` Pekka Enberg
2005-12-06 21:10 ` Paul Mackerras
2005-12-06 21:41 ` Pekka Enberg
2005-12-06 22:19 ` Paul Mackerras
2005-12-06 22:27 ` Arnd Bergmann
2005-12-07 2:26 ` Al Viro
2005-12-07 3:15 ` Paul Mackerras
2005-12-07 8:21 ` Pekka Enberg
2005-12-07 10:17 ` Al Viro [this message]
2005-12-06 22:14 ` Nathan Lynch
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=20051207101708.GJ27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=arjan@infradead.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=penberg@cs.helsinki.fi \
/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