From: Jeremy Kerr <jk@ozlabs.org>
To: Ben Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org
Subject: [GIT PULL] Please pull spufs merge branch
Date: Tue, 21 Oct 2008 11:46:42 +1100 [thread overview]
Message-ID: <200810211146.43634.jk@ozlabs.org> (raw)
Ben,
Please do a:
git pull \
git://git.kernel.org/pub/scm/linux/kernel/git/jk/spufs.git merge
For a few more spufs changes for .28
Cheers,
Jeremy
---
diffstat:
arch/powerpc/platforms/cell/spufs/file.c | 155 ++++++----
arch/powerpc/platforms/cell/spufs/run.c | 3
arch/powerpc/platforms/cell/spufs/sched.c | 24 +
arch/powerpc/platforms/cell/spufs/spufs.h | 1
arch/powerpc/platforms/cell/spufs/sputrace.c | 37 ++
5 files changed, 151 insertions(+), 69 deletions(-)
8 commits:
powerpc/spufs: sputrace: Only enable logging on open(), prevent
multiple openers
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: sputrace: Don't block until the read buffer is full
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: Use state_mutex for switch_log locking, and prevent
multiple openers
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: Don't require full buffer in switch_log read
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: Don't spu_acquire_saved unnecessarily in regs read
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: Use kmalloc rather than kzalloc for switch log buffer
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: Improve search of node for contexts with SPU affinity
Andre Detsch <adetsch@br.ibm.com>
powerpc/spufs: Explain conditional decrement of aff_sched_count
Andre Detsch <adetsch@br.ibm.com>
next reply other threads:[~2008-10-21 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 0:46 Jeremy Kerr [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-10 0:22 [GIT PULL] Please pull spufs merge branch Jeremy Kerr
2008-09-07 23:49 Jeremy Kerr
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=200810211146.43634.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=benh@kernel.crashing.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).