From: Arnd Bergmann <arnd.bergmann@de.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: Andrew Morton <akpm@osdl.org>, cbe-oss-dev@ozlabs.org
Subject: Re: [PATCH 0/3] spufs: don't need struct page for SPEs
Date: Wed, 7 Feb 2007 15:39:23 +0100 [thread overview]
Message-ID: <200702071539.23556.arnd.bergmann@de.ibm.com> (raw)
In-Reply-To: <1170823850.450936.293648942401.qpush@grosgo>
On Wednesday 07 February 2007 05:50, Benjamin Herrenschmidt wrote:
> I have no firm feeling on wether those should be in 2.6.21 or not,
> they are pre-requisite for some other work I'm doing with spufs but
> which won't be in 2.6.21 (well, I don't think it will be ready in time
> and it doesn't really matter) so I'm mostly posting this here for
> review/comment/backup :-) I would appreciate testing too, I did some
> tests here and they seem to pass but heh, the more the better.
I'd say they should go in. The code is clearly moving things into
the right direction. In fact, we have recently discovered a bug
in the SPU management that might be fixed by just applying your
patch, but that still needs to be investigated.
Arnd <><
prev parent reply other threads:[~2007-02-07 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 4:50 [PATCH 0/3] spufs: don't need struct page for SPEs Benjamin Herrenschmidt
2007-02-07 4:50 ` [PATCH 1/3] add vm_insert_pfn() Benjamin Herrenschmidt
2007-02-07 4:50 ` [PATCH 2/3] Add NOPFN_REFAULT result from vm_ops->nopfn() Benjamin Herrenschmidt
2007-02-07 4:50 ` [PATCH 3/3] spufs: remove need for struct page for SPEs Benjamin Herrenschmidt
2007-02-07 4:55 ` Benjamin Herrenschmidt
2007-02-07 14:52 ` [Cbe-oss-dev] " Christoph Hellwig
2007-02-07 22:21 ` Andrew Morton
2007-02-07 23:15 ` Benjamin Herrenschmidt
2007-02-09 3:59 ` [Cbe-oss-dev] " Benjamin Herrenschmidt
2007-02-07 14:39 ` Arnd Bergmann [this message]
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=200702071539.23556.arnd.bergmann@de.ibm.com \
--to=arnd.bergmann@de.ibm.com \
--cc=akpm@osdl.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).