From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: sfr@canb.auug.org.au
Subject: 'next' branch of powerpc4xx tree
Date: Sat, 1 Mar 2008 10:06:13 -0600 [thread overview]
Message-ID: <20080301100613.5de31a42@zod.rchland.ibm.com> (raw)
Since all the cool kids are doing it, I went and created a 'next' branch
in the powerpc4xx tree.
I'm basically using it as a place for me to queue things up as they are
submitted that look pretty good for going into the next release. While
I'll try hard not to rebase it, I can't guarantee that. Pull requests
to Paul will still come from a 'for-2.6.xx' branch when I think it's
time to send stuff upstream, so if you're looking for something stable
track that instead.
Stephen, if you'd like to add this to your -next tree feel free.
Hopefully it will usually be empty as I merge things into Paul's tree.
As of right now, I have the following patches in the 'next' branch:
David Gibson (1):
[POWERPC] Start removing linux,network-index in favour of aliases
Stefan Roese (5):
[POWERPC] 4xx: Add AMCC 460EX/460GT support to cputable.c & cpu_setup_44x.
[POWERPC] 4xx: Add AMCC Canyonlands 460EX eval board support to platforms/
[POWERPC] 4xx: Add Canyonlands DTS
[POWERPC] 4xx: Add 460EX PCIe support to 4xx pci driver
[POWERPC] 4xx: Add Canyonlands defconfig file
Soon to go in will be the Yosemite board port I did, and moving the
reset function to a common place for 4xx boards.
josh
next reply other threads:[~2008-03-01 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:06 Josh Boyer [this message]
2008-03-03 6:58 ` 'next' branch of powerpc4xx 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=20080301100613.5de31a42@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@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).