From: Jeremy Kerr <jk@ozlabs.org>
To: Paul Mackerras <paulus@samba.org>,
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: Fri, 10 Oct 2008 11:22:32 +1100 [thread overview]
Message-ID: <200810101122.33224.jk@ozlabs.org> (raw)
Hi Paul / Ben,
Please do a:
git pull \
git://git.kernel.org/pub/scm/linux/kernel/git/jk/spufs.git merge
For a few spufs fixes for 2.6.28
Cheers,
Jeremy
---
diffstat:
arch/powerpc/platforms/cell/spufs/inode.c | 11 ++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
3 commits:
powerpc/spufs: set nlink count for spufs root correctly
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: use inc_nlink
Jeremy Kerr <jk@ozlabs.org>
powerpc/spufs: add a missing mutex_unlock
Kou Ishizaki <kou.ishizaki@toshiba.co.jp>
next reply other threads:[~2008-10-10 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 0:22 Jeremy Kerr [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-21 0:46 [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=200810101122.33224.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).