linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Albert Herranz <albert_herranz@yahoo.es>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v2 0/6] powerpc: nintendo wii support
Date: Sat, 12 Dec 2009 01:18:44 +0100	[thread overview]
Message-ID: <4B22E164.1070606@yahoo.es> (raw)
In-Reply-To: <fa686aa40912111552m28d1cc40we072cebef675f100@mail.gmail.com>

Grant Likely wrote:
> Hi Albert.
> 

Hi,

> I'm ready to pick up your Gamecube and Wii patch sets for merging.
> You seem to have 4 distinct patch sets.  What order do they need to be
> applied in, and what kernel version are they based on?
> 

The patches were based on 2.6.32-rc8.
The apply order should be:

v2 powerpc: nintendo gamecube support
 powerpc: gamecube/wii: usbgecko bootwrapper console support
 powerpc: gamecube: device tree
 powerpc: gamecube: bootwrapper bits
 powerpc: gamecube/wii: introduce GAMECUBE_COMMON
 powerpc: gamecube/wii: declare as non-coherent platforms
 powerpc: gamecube/wii: do not include PCI support
 powerpc: gamecube/wii: udbg support for usbgecko
 powerpc: gamecube/wii: flipper interrupt controller support
 powerpc: gamecube: platform support
 powerpc: gamecube: default config

v2 powerpc: nintendo wii support
 powerpc: wii: device tree
 powerpc: wii: bootwrapper bits
 powerpc: broadway processor support
 powerpc: wii: hollywood interrupt controller support
 powerpc: wii: platform support
 powerpc: wii: default config

v4 rework of usbgecko-based early debug
 powerpc: reserve fixmap entries for early debug
 powerpc: gamecube/wii: early debugging using usbgecko

v2 powerpc: wii: mem2 as ram support
 wii: bootwrapper: add fixup to calc useable mem2
 wii: use both mem1 and mem2 as ram
 powerpc: allow ioremap within reserved memory regions
 powerpc: wii: allow ioremap within the memory hole

But if you prefer it, I can re-send them as one patch set again rebased on top of v2.6.32.

> Thanks,
> g.

Thanks,
Albert

  reply	other threads:[~2009-12-12  0:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 22:47 [RFC PATCH v2 0/6] powerpc: nintendo wii support Albert Herranz
2009-12-03 22:47 ` [RFC PATCH v2 1/6] powerpc: wii: device tree Albert Herranz
2009-12-04 15:25   ` Segher Boessenkool
2009-12-04 16:54     ` Albert Herranz
2009-12-11 21:59   ` Benjamin Herrenschmidt
2009-12-03 22:47 ` [RFC PATCH v2 2/6] powerpc: wii: bootwrapper bits Albert Herranz
2009-12-09 16:23   ` Segher Boessenkool
2009-12-11 21:59   ` Benjamin Herrenschmidt
2009-12-03 22:47 ` [RFC PATCH v2 3/6] powerpc: broadway processor support Albert Herranz
2009-12-11 21:59   ` Benjamin Herrenschmidt
2009-12-03 22:47 ` [RFC PATCH v2 4/6] powerpc: wii: hollywood interrupt controller support Albert Herranz
2009-12-11 22:01   ` Benjamin Herrenschmidt
2009-12-12 15:12   ` Segher Boessenkool
2009-12-03 22:47 ` [RFC PATCH v2 5/6] powerpc: wii: platform support Albert Herranz
2009-12-12 15:14   ` Segher Boessenkool
2009-12-03 22:47 ` [RFC PATCH v2 6/6] powerpc: wii: default config Albert Herranz
2009-12-11 22:02   ` Benjamin Herrenschmidt
2009-12-11 23:52 ` [RFC PATCH v2 0/6] powerpc: nintendo wii support Grant Likely
2009-12-12  0:18   ` Albert Herranz [this message]
2009-12-12  6:47     ` Grant Likely
2009-12-12  9:35       ` Albert Herranz

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=4B22E164.1070606@yahoo.es \
    --to=albert_herranz@yahoo.es \
    --cc=grant.likely@secretlab.ca \
    --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).