linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yibin Gong <yibin.gong@freescale.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vinod Koul <vinod.koul@intel.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: linux-next: build failure after merge of the slave-dma tree
Date: Mon, 16 Feb 2015 01:48:56 +0000	[thread overview]
Message-ID: <EB2E1ED4-00E1-4BDE-9B0D-8CB8912674B7@freescale.com> (raw)
In-Reply-To: <20150216120934.3f4dc936@canb.auug.org.au>

Hi Stephen,
    Thanks for you report. I have notice it and sent the v4 patch review yesterday.

发自我的 iPhone

> 在 2015年2月16日，09:09，Stephen Rothwell <sfr@canb.auug.org.au> 写道：
> 
> Hi Vinod,
> 
> After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig)
> failed like this:
> 
> drivers/dma/imx-sdma.c: In function 'sdma_run_channel0':
> drivers/dma/imx-sdma.c:535:57: error: macro "readl" passed 2 arguments, but takes just 1
>  if (readl(SDMA_H_CONFIG_CSM, sdma->regs + SDMA_H_CONFIG) == 0)
>                                                         ^
> drivers/dma/imx-sdma.c:535:6: error: 'readl' undeclared (first use in this function)
>  if (readl(SDMA_H_CONFIG_CSM, sdma->regs + SDMA_H_CONFIG) == 0)
>      ^
> 
> Caused by commit 66a073b6478d ("dmaengine: imx-sdma: switch to dynamic
> context mode after script loaded").
> 
> I have used the slave-dma tree from next-20150213 for today.
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au

  reply	other threads:[~2015-02-16  1:48 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  1:09 linux-next: build failure after merge of the slave-dma tree Stephen Rothwell
2015-02-16  1:48 ` Yibin Gong [this message]
2015-02-16  4:06   ` Vinod Koul
  -- 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: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
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-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-06-22  3:00 Stephen Rothwell
2012-06-22  5:01 ` Vinod Koul
2012-06-25  1:21   ` Zhangfei Gao
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=EB2E1ED4-00E1-4BDE-9B0D-8CB8912674B7@freescale.com \
    --to=yibin.gong@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sfr@canb.auug.org.au \
    --cc=vinod.koul@intel.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 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).