From: Michael Ellerman <mpe@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org
Subject: next is open
Date: Tue, 21 Jul 2015 13:18:07 +1000 [thread overview]
Message-ID: <1437448687.30722.5.camel@ellerman.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Hi folks,
Just letting you know that powerpc next is open.
So now is the time to start sending patches for 4.3.
Ben & I now have a shared powerpc tree on kernel.org, so that is the place you
should be looking at if you want to see what's in next:
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git
For now you should ignore our personal trees unless we tell you otherwise.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2015-07-21 3:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1437448687.30722.5.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--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).