From: Christoph Hellwig <hch@lst.de>
To: arndb@arndb.de
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] spufs: fix compile
Date: Fri, 7 Apr 2006 13:54:31 +0200 [thread overview]
Message-ID: <20060407115431.GA28381@lst.de> (raw)
In-Reply-To: <20060406134810.GB8552@lst.de>
On Thu, Apr 06, 2006 at 03:48:10PM +0200, Christoph Hellwig wrote:
> The current tree isn't exctly sure about the arguments to
> alloc_spu_context, let it agree on the no-arguments version.
Please ignore all these patches, I had a messed up tree.
prev parent reply other threads:[~2006-04-07 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 13:48 [PATCH] spufs: fix compile Christoph Hellwig
2006-04-07 11:54 ` Christoph Hellwig [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=20060407115431.GA28381@lst.de \
--to=hch@lst.de \
--cc=arndb@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.