linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Giuseppe Coviello <cjg@cruxppc.org>
Subject: Re: [PATCH] Sam440ep support
Date: Tue, 06 May 2008 09:38:02 +1000	[thread overview]
Message-ID: <1210030682.21644.116.camel@pasglop> (raw)
In-Reply-To: <6DA6B1DA-11B5-4B89-88AD-561B4D17B33B@kernel.crashing.org>


On Mon, 2008-05-05 at 13:27 -0500, Kumar Gala wrote:
> On May 5, 2008, at 1:23 PM, Giuseppe Coviello wrote:
> 
> > This patch adds the support for the sam440ep board.
> >
> > arch/powerpc/boot/Makefile                  |    5 +-
> > arch/powerpc/boot/cuboot-sam440ep.c         |   35 +
> > arch/powerpc/boot/dts/sam440ep.dts          |  292 ++++++
> > arch/powerpc/boot/sam440ep.c                |   53 +
> > arch/powerpc/configs/44x/sam440ep_defconfig | 1429 ++++++++++++++++++ 
> > +++++++++
> > arch/powerpc/platforms/44x/Kconfig          |    9 +
> > arch/powerpc/platforms/44x/Makefile         |    1 +
> > arch/powerpc/platforms/44x/sam440ep.c       |   66 ++
> > arch/powerpc/sysdev/Makefile                |    1 +
> > arch/powerpc/sysdev/sam440ep.c              |  112 +++
> > include/asm-powerpc/dma-mapping.h           |   30 +
> > sound/core/memalloc.c                       |   31 +-
> 
> The changes to dma-mapping.h and sound/core/memalloc.c need to be  
> explained and odds are will not go in as is.

They can certainly not be merged in their current form. Guiseppe, what
is the underlying problem, can you describe it in details ?

Ben.

  parent reply	other threads:[~2008-05-05 23:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 18:23 [PATCH] Sam440ep support Giuseppe Coviello
2008-05-05 18:27 ` Kumar Gala
2008-05-05 19:50   ` Gerhard Pircher
2008-05-05 23:44     ` Benjamin Herrenschmidt
2008-05-06  7:51       ` Gerhard Pircher
2008-05-06  8:48         ` Benjamin Herrenschmidt
2008-05-06  9:16           ` Gerhard Pircher
2008-05-06 10:12             ` Benjamin Herrenschmidt
2008-05-06 11:14               ` Takashi Iwai
2008-05-06 11:25                 ` Benjamin Herrenschmidt
2008-05-06 11:27                   ` Benjamin Herrenschmidt
2008-05-06 11:31                   ` Takashi Iwai
2008-05-06 11:34                     ` Benjamin Herrenschmidt
2008-05-14 12:26             ` ALSA fixes for non-coherent archs (Re: [PATCH] Sam440ep support) Takashi Iwai
2008-05-14 12:50               ` Gerhard Pircher
2008-05-14 21:01               ` Gerhard Pircher
2008-05-15  5:42                 ` Takashi Iwai
2008-05-19 17:23               ` Giuseppe Coviello
2008-05-20 12:48                 ` Takashi Iwai
2008-05-05 23:38   ` Benjamin Herrenschmidt [this message]
2008-05-05 18:54 ` [PATCH] Sam440ep support Josh Boyer
2008-05-05 23:40   ` Benjamin Herrenschmidt
2008-05-06  0:09     ` Josh Boyer
2008-05-05 23:36 ` Benjamin Herrenschmidt
2008-05-06  4:18   ` Sean MacLennan
2008-05-06 16:37 ` Giuseppe Coviello
2008-05-09 15:53   ` Giuseppe Coviello
2008-05-09 20:26     ` Josh Boyer
2008-05-19 12:47   ` Josh Boyer
2008-05-19 15:20     ` Giuseppe Coviello
2008-05-20 12:50       ` Josh Boyer
2008-05-20 13:34         ` Josh Boyer
2008-05-22 17:51           ` Giuseppe Coviello

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=1210030682.21644.116.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=cjg@cruxppc.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@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).