From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: power-next
Date: Tue, 20 Sep 2011 16:46:14 +1000 [thread overview]
Message-ID: <1316501174.7975.32.camel@pasglop> (raw)
Hi folks !
So I've finally got to setup a branch on github for powerpc next.
I've also committed a bunch of stuff to it, so here it is. I'll go back
to kernel.org as soon as it's been fixed.
https://github.com/ozbenh/linux/commits/next
Cheers,
Ben.
next reply other threads:[~2011-09-20 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 6:46 Benjamin Herrenschmidt [this message]
2011-09-20 6:48 ` power-next Benjamin Herrenschmidt
2011-09-20 10:30 ` power-next Stephen Rothwell
2011-09-20 18:45 ` power-next Benjamin Herrenschmidt
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=1316501174.7975.32.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.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).