All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhangfei Gao <zgao6@marvell.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Leo Yan <leoy@marvell.com>, Qiao Zhou <zhouqiao@marvell.com>
Subject: Re: linux-next: build failure after merge of the slave-dma tree
Date: Mon, 25 Jun 2012 09:21:20 +0800	[thread overview]
Message-ID: <1340587280.14586.9.camel@apse> (raw)
In-Reply-To: <1340341305.1562.2.camel@vkoul-udesk3>

On Thu, 2012-06-21 at 22:01 -0700, Vinod Koul wrote:
> On Fri, 2012-06-22 at 13:00 +1000, Stephen Rothwell wrote:
> > Hi Vinod,
> > 
> > After merging the slave-dma tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/dma/mmp_tdma.c:21:27: fatal error: mach/regs-icu.h: No such file or directory
> > 
> > Caused by commit c6da0ba8dfc8 ("dmaengine: mmp_tdma: add mmp tdma
> > support").
> > 
> > I have used the slave-dma tree from next-20120621 for today.
> Thanks Stephen,
> 
> It should not build for this target!. I will added the below patch to
> fix the failure
> 
> >From 0efc8562577cd6a022b8b42d58fcf58ffc2a91d3 Mon Sep 17 00:00:00 2001
> From: Vinod Koul <vinod.koul@linux.intel.com>
> Date: Fri, 22 Jun 2012 10:29:53 +0530
> Subject: [PATCH] dmaengine: mmp_tdma: fix the arch dependency
> 
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Vinod Koul <vinod.koul@linux.intel.com>
> ---
>  drivers/dma/Kconfig |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
> index 90fec0e..d45cf1b 100644
> --- a/drivers/dma/Kconfig
> +++ b/drivers/dma/Kconfig
> @@ -276,7 +276,7 @@ config DMA_SA11X0
>  
>  config MMP_TDMA
>  	bool "MMP Two-Channel DMA support"
> -	default ARCH_MMP
> +	depends on ARCH_MMP
>  	select DMA_ENGINE
>  	help
>  	  Support the MMP Two-Channel DMA engine.
> -- 
> 1.7.0.4
> 

Thanks Vinod and Stephen, sorry for the trouble.
> 

  reply	other threads:[~2012-06-25  1:22 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22  3:00 linux-next: build failure after merge of the slave-dma tree Stephen Rothwell
2012-06-22  5:01 ` Vinod Koul
2012-06-25  1:21   ` Zhangfei Gao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-04  7:31 Stephen Rothwell
2019-07-06 13:43 ` Robin Gong
2019-07-06 14:43   ` Vinod Koul
2019-07-08  2:01     ` Robin Gong
2019-07-08  4:09       ` Vinod Koul
2019-07-08  1:22 ` Robin Gong
2019-07-08  3:06   ` zhangfei
2019-07-08  4:17     ` Vinod Koul
2019-07-08  4:54       ` Robin Gong
2019-07-08  4:48     ` Robin Gong
2018-10-04  5:44 Stephen Rothwell
2018-10-04  6:13 ` Vinod
2017-08-22  5:36 Stephen Rothwell
2017-08-22 16:39 ` Vinod Koul
2016-09-16  3:18 Stephen Rothwell
2016-09-16  8:34 ` Peter Griffin
2016-09-19 16:38   ` Vinod Koul
2015-10-15  0:51 Stephen Rothwell
2015-10-15  3:35 ` Koul, Vinod
2015-10-15  3:35   ` Koul, Vinod
2015-10-15  3:51   ` Stephen Rothwell
2015-10-15 14:07     ` Arnd Bergmann
2015-10-15 14:27       ` Stephen Rothwell
2015-08-06  2:22 Stephen Rothwell
2015-08-06  3:00 ` Vinod Koul
2015-08-24  6:53   ` Maxime Ripard
2015-08-24  8:11     ` Vinod Koul
2015-08-24  9:21       ` Maxime Ripard
2015-02-16  1:09 Stephen Rothwell
2015-02-16  1:48 ` Yibin Gong
2015-02-16  1:48   ` Yibin Gong
2015-02-16  4:06   ` Vinod Koul
2014-12-09  3:48 Stephen Rothwell
2014-12-09  4:47 ` Vinod Koul
2014-11-10  0:58 Stephen Rothwell
2014-11-10  5:06 ` Vinod Koul
2014-11-12 13:23   ` Ludovic Desroches
2014-11-12 13:23     ` Ludovic Desroches
2014-09-12  3:17 Stephen Rothwell
2014-09-15  9:51 ` Geert Uytterhoeven
2014-07-28  2:18 Stephen Rothwell
2014-07-28  7:16 ` Vinod Koul
2014-07-28 11:56   ` Maxime Ripard
2013-04-02  1:57 Stephen Rothwell
2013-04-02  1:38 ` Vinod Koul
2013-01-07  0:26 Stephen Rothwell
2013-01-07 14:00 ` Vinod Koul
2012-03-27  0:52 Stephen Rothwell
2012-03-27  8:33 ` Vinod Koul

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=1340587280.14586.9.camel@apse \
    --to=zgao6@marvell.com \
    --cc=leoy@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vinod.koul@linux.intel.com \
    --cc=zhouqiao@marvell.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.