From: Josh Boyer <jwboyer@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Please pull 'next' branch of new 4xx tree
Date: Wed, 30 Nov 2011 10:14:52 -0500 [thread overview]
Message-ID: <CA+5PVA6ahzxWHqBiESw8x7RVC1n8hjqBPvMnQ8qfb=bpwMeuzQ@mail.gmail.com> (raw)
Hi Ben,
I have a new 4xx tree setup now. Two small commits for the next
branch are queued up. I'd like to get the patch series from Suzie and
Tony included soon as well, but thought I'd start with these to get
things rolling.
Stephen, can you switch the linux-next tree to use this instead?
josh
The following changes since commit fa8cbaaf5a68f62db3f9a8444ecbb940b47984cb:
powerpc+sparc64/mm: Remove hack in mmap randomize layout (2011-11-28
11:42:09 +1100)
are available in the git repository at:
git://git.infradead.org/users/jwboyer/powerpc-4xx.git next
Josh Boyer (1):
MAINTAINERS: Update PowerPC 4xx git tree
Tanmay Inamdar (1):
powerpc/40x: Add APM8018X SOC support
MAINTAINERS | 2 +-
arch/powerpc/boot/dts/klondike.dts | 227 +++++++++++++++++++++++++++
arch/powerpc/configs/40x/klondike_defconfig | 55 +++++++
arch/powerpc/kernel/cputable.c | 13 ++
arch/powerpc/platforms/40x/Kconfig | 11 ++
arch/powerpc/platforms/40x/ppc40x_simple.c | 1 +
6 files changed, 308 insertions(+), 1 deletions(-)
create mode 100644 arch/powerpc/boot/dts/klondike.dts
create mode 100644 arch/powerpc/configs/40x/klondike_defconfig
next reply other threads:[~2011-11-30 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 15:14 Josh Boyer [this message]
2011-11-30 23:41 ` Please pull 'next' branch of new 4xx tree Stephen Rothwell
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='CA+5PVA6ahzxWHqBiESw8x7RVC1n8hjqBPvMnQ8qfb=bpwMeuzQ@mail.gmail.com' \
--to=jwboyer@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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).