RE: linux-next: build failure after merge of the slave-dma tree

On 2019/7/8 12:17 Vinod Koul wrote: > On 08-07-19, 11:06, zhangfei wrote: > > Hi, Robin > > > > On 2019/7/8 上午9:22, Robin Gong wrote: > > > Hi Stephen, > > > That's caused by 'of_irq_count' NOT export to global symbol, and > > > I'm curious why it has been here for so long since Zhangfei found

RE: linux-next: build failure after merge of the slave-dma tree

On 2019/7/8 11:06 AM, zhangfei wrote: > Hi, Robin > > On 2019/7/8 上午9:22, Robin Gong wrote: > > Hi Stephen, > > That's caused by 'of_irq_count' NOT export to global symbol, and I'm > > curious why it has been here for so long since Zhangfei found it in > > 2015. > >

Re: linux-next: build failure after merge of the slave-dma tree

On 08-07-19, 11:06, zhangfei wrote: > Hi, Robin > > On 2019/7/8 上午9:22, Robin Gong wrote: > > Hi Stephen, > > That's caused by 'of_irq_count' NOT export to global symbol, and I'm > > curious why it has been > > here for so long since Zhangfei found it in 2015. > >

Re: linux-next: build failure after merge of the slave-dma tree

On 08-07-19, 02:01, Robin Gong wrote: > On 06-07-19, 22:43, Vinod Koul wrote: > > > That's caused by 'of_irq_count' NOT export to global symbol, and I'm > > > curious why it has been here for so long since Zhangfei found it in > > > 2015. > > >

Re: linux-next: build failure after merge of the slave-dma tree

Hi, Robin On 2019/7/8 上午9:22, Robin Gong wrote: Hi Stephen, That's caused by 'of_irq_count' NOT export to global symbol, and I'm curious why it has been here for so long since Zhangfei found it in 2015. https://patchwork.kernel.org/patch/7404681/ Hi Rob, Is there something I

RE: linux-next: build failure after merge of the slave-dma tree

On 06-07-19, 22:43, Vinod Koul wrote: > > That's caused by 'of_irq_count' NOT export to global symbol, and I'm > > curious why it has been here for so long since Zhangfei found it in > > 2015. > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc > > >

RE: linux-next: build failure after merge of the slave-dma tree

Hi Stephen, That's caused by 'of_irq_count' NOT export to global symbol, and I'm curious why it has been here for so long since Zhangfei found it in 2015. https://patchwork.kernel.org/patch/7404681/ Hi Rob, Is there something I miss so that Zhangfei's patch not accepted finally?

Re: linux-next: build failure after merge of the slave-dma tree

On 06-07-19, 13:43, Robin Gong wrote: > Hi Stephen, Please **do not** top post! > That's caused by 'of_irq_count' NOT export to global symbol, and I'm > curious why it has been > here for so long since Zhangfei found it in 2015. > https://patchwork.kernel.org/patch/7404681/ Yes this

RE: linux-next: build failure after merge of the slave-dma tree

Hi Stephen, That's caused by 'of_irq_count' NOT export to global symbol, and I'm curious why it has been here for so long since Zhangfei found it in 2015. https://patchwork.kernel.org/patch/7404681/ Hi Rob, Is there something I miss so that Zhangfei's patch not accepted finally?

linux-next: build failure after merge of the slave-dma tree

Hi all, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "of_irq_count" [drivers/dma/fsl-edma.ko] undefined! Caused by commit 7144afd025b2 ("dmaengine: fsl-edma: add i.mx7ulp edma2 version support") I have reverted that commit for

Re: linux-next: build failure after merge of the slave-dma tree

Hi Stephen, On 04-10-18, 15:44, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/dma/fsl-edma.c:67: warning: "EDMA_SEEI_SEEI" redefined > #define EDMA_SEEI_SEEI(x) ((x) & 0x1F) > > In

Re: linux-next: build failure after merge of the slave-dma tree

Hi Stephen, On 04-10-18, 15:44, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/dma/fsl-edma.c:67: warning: "EDMA_SEEI_SEEI" redefined > #define EDMA_SEEI_SEEI(x) ((x) & 0x1F) > > In

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/dma/fsl-edma.c:67: warning: "EDMA_SEEI_SEEI" redefined #define EDMA_SEEI_SEEI(x) ((x) & 0x1F) In file included from drivers/dma/fsl-edma.c:25:

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/dma/fsl-edma.c:67: warning: "EDMA_SEEI_SEEI" redefined #define EDMA_SEEI_SEEI(x) ((x) & 0x1F) In file included from drivers/dma/fsl-edma.c:25:

Re: linux-next: build failure after merge of the slave-dma tree

On Tue, Aug 22, 2017 at 03:36:54PM +1000, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/dma/dmaengine.h:9:0, > from drivers/dma/altera-msgdma.c:27: >

Re: linux-next: build failure after merge of the slave-dma tree

On Tue, Aug 22, 2017 at 03:36:54PM +1000, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from drivers/dma/dmaengine.h:9:0, > from drivers/dma/altera-msgdma.c:27: >

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/dma/dmaengine.h:9:0, from drivers/dma/altera-msgdma.c:27: drivers/dma/altera-msgdma.c: In function 'msgdma_probe':

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/dma/dmaengine.h:9:0, from drivers/dma/altera-msgdma.c:27: drivers/dma/altera-msgdma.c: In function 'msgdma_probe':

Re: linux-next: build failure after merge of the slave-dma tree

On Fri, Sep 16, 2016 at 09:34:44AM +0100, Peter Griffin wrote: > Hi Vinod & Stephen, > > On Fri, 16 Sep 2016, Stephen Rothwell wrote: > > > Hi Vinod, > > > > After merging the slave-dma tree, today's linux-next build (arm > > multi_v7_defconfig build) failed like this: > > FYI Patch 17 of 19

Re: linux-next: build failure after merge of the slave-dma tree

On Fri, Sep 16, 2016 at 09:34:44AM +0100, Peter Griffin wrote: > Hi Vinod & Stephen, > > On Fri, 16 Sep 2016, Stephen Rothwell wrote: > > > Hi Vinod, > > > > After merging the slave-dma tree, today's linux-next build (arm > > multi_v7_defconfig build) failed like this: > > FYI Patch 17 of 19

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod & Stephen, On Fri, 16 Sep 2016, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (arm > multi_v7_defconfig build) failed like this: FYI Patch 17 of 19 in the fdma series "drm/virtio: kconfig: Fix recursive dependency issue." [1],

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod & Stephen, On Fri, 16 Sep 2016, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (arm > multi_v7_defconfig build) failed like this: FYI Patch 17 of 19 in the fdma series "drm/virtio: kconfig: Fix recursive dependency issue." [1],

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig build) failed like this: drivers/video/fbdev/Kconfig:5:error: recursive dependency detected! For a resolution refer to Documentation/kbuild/kconfig-language.txt subsection "Kconfig recursive dependency

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig build) failed like this: drivers/video/fbdev/Kconfig:5:error: recursive dependency detected! For a resolution refer to Documentation/kbuild/kconfig-language.txt subsection "Kconfig recursive dependency

Re: linux-next: build failure after merge of the slave-dma tree

Hi Arnd, On Thu, 15 Oct 2015 16:07:51 +0200 Arnd Bergmann wrote: > > I've added a workaround to the asm-generic tree, no need to worry about > it for now. We can change over the remaining users of > asm-generic/io-64-nonatomic-lo-hi.h for the following merge window and > then remove the wrapper.

Re: linux-next: build failure after merge of the slave-dma tree

On Thursday 15 October 2015 14:51:42 Stephen Rothwell wrote: > Hi Vinod, > > On Thu, 15 Oct 2015 03:35:42 + "Koul, Vinod" wrote: > > > > So should I ask Linus to apply this fix once merge window opens or you will > > send > > this, how do we go about fixing this one > > > > Or should I

Re: linux-next: build failure after merge of the slave-dma tree

On Thursday 15 October 2015 14:51:42 Stephen Rothwell wrote: > Hi Vinod, > > On Thu, 15 Oct 2015 03:35:42 + "Koul, Vinod" wrote: > > > > So should I ask Linus to apply this fix once merge window opens or you will > > send > > this, how do we go about fixing this one >

Re: linux-next: build failure after merge of the slave-dma tree

Hi Arnd, On Thu, 15 Oct 2015 16:07:51 +0200 Arnd Bergmann wrote: > > I've added a workaround to the asm-generic tree, no need to worry about > it for now. We can change over the remaining users of > asm-generic/io-64-nonatomic-lo-hi.h for the following merge window and > then

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod, On Thu, 15 Oct 2015 03:35:42 + "Koul, Vinod" wrote: > > So should I ask Linus to apply this fix once merge window opens or you will > send > this, how do we go about fixing this one :) > > Or should I merge the above commit from asm-generic tree? Up to you. Though you should

Re: linux-next: build failure after merge of the slave-dma tree

On Thu, 2015-10-15 at 11:51 +1100, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/dma/idma64.h:19:47: fatal error: asm-generic/io-64-nonatomic-lo-hi.h: > No > such file or directory >

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/idma64.h:19:47: fatal error: asm-generic/io-64-nonatomic-lo-hi.h: No such file or directory #include ^ Caused by commit

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/idma64.h:19:47: fatal error: asm-generic/io-64-nonatomic-lo-hi.h: No such file or directory #include ^ Caused by commit

Re: linux-next: build failure after merge of the slave-dma tree

On Thu, 2015-10-15 at 11:51 +1100, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/dma/idma64.h:19:47: fatal error: asm-generic/io-64-nonatomic-lo-hi.h: > No > such file or directory >

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod, On Thu, 15 Oct 2015 03:35:42 + "Koul, Vinod" wrote: > > So should I ask Linus to apply this fix once merge window opens or you will > send > this, how do we go about fixing this one :) > > Or should I merge the above commit from asm-generic tree? Up to you.

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Aug 24, 2015 at 01:41:43PM +0530, Vinod Koul wrote: > On Mon, Aug 24, 2015 at 08:53:59AM +0200, Maxime Ripard wrote: > > > I am dropping this commit now, it need to be fixed to take into account > > > Cyrille work on remove tx_width and this patch should be updated to > > > reflect > > >

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Aug 24, 2015 at 08:53:59AM +0200, Maxime Ripard wrote: > > I am dropping this commit now, it need to be fixed to take into account > > Cyrille work on remove tx_width and this patch should be updated to reflect > > that > > I'll send an updated version today, is there some time left for

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod, On Thu, Aug 06, 2015 at 08:30:27AM +0530, Vinod Koul wrote: > On Thu, Aug 06, 2015 at 12:22:03PM +1000, Stephen Rothwell wrote: > > Hi Vinod, > > > > After merging the slave-dma tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > >

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod, On Thu, Aug 06, 2015 at 08:30:27AM +0530, Vinod Koul wrote: On Thu, Aug 06, 2015 at 12:22:03PM +1000, Stephen Rothwell wrote: Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/dma/at_hdmac.c: In

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Aug 24, 2015 at 08:53:59AM +0200, Maxime Ripard wrote: I am dropping this commit now, it need to be fixed to take into account Cyrille work on remove tx_width and this patch should be updated to reflect that I'll send an updated version today, is there some time left for this to

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Aug 24, 2015 at 01:41:43PM +0530, Vinod Koul wrote: On Mon, Aug 24, 2015 at 08:53:59AM +0200, Maxime Ripard wrote: I am dropping this commit now, it need to be fixed to take into account Cyrille work on remove tx_width and this patch should be updated to reflect that

Re: linux-next: build failure after merge of the slave-dma tree

On Thu, Aug 06, 2015 at 12:22:03PM +1000, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/dma/at_hdmac.c: In function 'atc_prep_dma_memset': > drivers/dma/at_hdmac.c:960:6: error: 'struct

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/dma/at_hdmac.c: In function 'atc_prep_dma_memset': drivers/dma/at_hdmac.c:960:6: error: 'struct at_desc' has no member named 'tx_width' desc->tx_width = 2; ^ Caused

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/dma/at_hdmac.c: In function 'atc_prep_dma_memset': drivers/dma/at_hdmac.c:960:6: error: 'struct at_desc' has no member named 'tx_width' desc-tx_width = 2; ^ Caused by

Re: linux-next: build failure after merge of the slave-dma tree

On Thu, Aug 06, 2015 at 12:22:03PM +1000, Stephen Rothwell wrote: Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/dma/at_hdmac.c: In function 'atc_prep_dma_memset': drivers/dma/at_hdmac.c:960:6: error: 'struct

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Feb 16, 2015 at 01:48:56AM +, Yibin Gong wrote: > 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 写道： > > > > Hi Vinod, > > > > After merging the slave-dma tree, today's

Re: linux-next: build failure after merge of the slave-dma tree

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 写道： > > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (arm > multi_v7_defconfig) > failed like this: > >

linux-next: build failure after merge of the slave-dma tree

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,

linux-next: build failure after merge of the slave-dma tree

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,

Re: linux-next: build failure after merge of the slave-dma tree

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 s...@canb.auug.org.au 写道： Hi Vinod, After merging the slave-dma tree, today's linux-next build (arm multi_v7_defconfig) failed like this:

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Feb 16, 2015 at 01:48:56AM +, Yibin Gong wrote: 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 s...@canb.auug.org.au 写道： Hi Vinod, After merging the slave-dma tree,

Re: linux-next: build failure after merge of the slave-dma tree

On Tue, Dec 09, 2014 at 02:48:17PM +1100, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) failed like this: I did merge the next-20141208 wth this new code and pushed. Found and resolved the same merg conflict as you :)

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/spi/spi-atmel.c: In function 'atmel_spi_stop_dma': drivers/spi/spi-atmel.c:485:26: error: 'struct dma_device' has no member named 'device_control'

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/spi/spi-atmel.c: In function 'atmel_spi_stop_dma': drivers/spi/spi-atmel.c:485:26: error: 'struct dma_device' has no member named 'device_control'

Re: linux-next: build failure after merge of the slave-dma tree

On Tue, Dec 09, 2014 at 02:48:17PM +1100, Stephen Rothwell wrote: Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: I did merge the next-20141208 wth this new code and pushed. Found and resolved the same merg conflict as you :) Feng'd

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod, On Mon, Nov 10, 2014 at 10:36:16AM +0530, Vinod Koul wrote: > On Mon, Nov 10, 2014 at 11:58:46AM +1100, Stephen Rothwell wrote: > > Hi Vinod, > > > > After merging the slave-dma tree, today's linux-next build (x86_64 > > allmodconfig) > > failed like this: > > > >

Re: linux-next: build failure after merge of the slave-dma tree

Hi Vinod, On Mon, Nov 10, 2014 at 10:36:16AM +0530, Vinod Koul wrote: On Mon, Nov 10, 2014 at 11:58:46AM +1100, Stephen Rothwell wrote: Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/at_xdmac.c: In

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Nov 10, 2014 at 11:58:46AM +1100, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) > failed like this: > > drivers/dma/at_xdmac.c: In function 'at_xdmac_off': > drivers/dma/at_xdmac.c:317:2: error: implicit

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/at_xdmac.c: In function 'at_xdmac_off': drivers/dma/at_xdmac.c:317:2: error: implicit declaration of function 'writel_relaxed' [-Werror=implicit-function-declaration]

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/at_xdmac.c: In function 'at_xdmac_off': drivers/dma/at_xdmac.c:317:2: error: implicit declaration of function 'writel_relaxed' [-Werror=implicit-function-declaration]

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Nov 10, 2014 at 11:58:46AM +1100, Stephen Rothwell wrote: Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/at_xdmac.c: In function 'at_xdmac_off': drivers/dma/at_xdmac.c:317:2: error: implicit declaration of

Re: linux-next: build failure after merge of the slave-dma tree

On Fri, Sep 12, 2014 at 5:17 AM, Stephen Rothwell wrote: > After merging the slave-dma tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > > drivers/spi/spi-pxa2xx-pci.c:70:3: error: unknown field 'max_clk_rate' > specified in initializer >.max_clk_rate =

Re: linux-next: build failure after merge of the slave-dma tree

On Fri, Sep 12, 2014 at 5:17 AM, Stephen Rothwell s...@canb.auug.org.au wrote: After merging the slave-dma tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/spi/spi-pxa2xx-pci.c:70:3: error: unknown field 'max_clk_rate' specified in initializer

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/spi/spi-pxa2xx-pci.c:70:3: error: unknown field 'max_clk_rate' specified in initializer .max_clk_rate = 5000, ^ Caused by commit bfe607a528ba ("spi/pxa2xx-pci:

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/spi/spi-pxa2xx-pci.c:70:3: error: unknown field 'max_clk_rate' specified in initializer .max_clk_rate = 5000, ^ Caused by commit bfe607a528ba (spi/pxa2xx-pci: Add

Re: linux-next: build failure after merge of the slave-dma tree

Hi, On Mon, Jul 28, 2014 at 12:46:22PM +0530, Vinod Koul wrote: > On Mon, Jul 28, 2014 at 12:18:56PM +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/sun6i-dma.c: In

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Jul 28, 2014 at 12:18:56PM +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/sun6i-dma.c: In function 'sun6i_dma_dump_chan_regs': > drivers/dma/sun6i-dma.c:203:2: error:

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Jul 28, 2014 at 12:18:56PM +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/sun6i-dma.c: In function 'sun6i_dma_dump_chan_regs': drivers/dma/sun6i-dma.c:203:2: error: implicit

Re: linux-next: build failure after merge of the slave-dma tree

Hi, On Mon, Jul 28, 2014 at 12:46:22PM +0530, Vinod Koul wrote: On Mon, Jul 28, 2014 at 12:18:56PM +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/sun6i-dma.c: In function

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/sun6i-dma.c: In function 'sun6i_dma_dump_chan_regs': drivers/dma/sun6i-dma.c:203:2: error: implicit declaration of function '__virt_to_phys'

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/sun6i-dma.c: In function 'sun6i_dma_dump_chan_regs': drivers/dma/sun6i-dma.c:203:2: error: implicit declaration of function '__virt_to_phys'

Re: linux-next: build failure after merge of the slave-dma tree

On Tue, Apr 02, 2013 at 12:57:11PM +1100, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/netdevice.h:38:0, > from arch/x86/net/bpf_jit_comp.c:12:

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/netdevice.h:38:0, from arch/x86/net/bpf_jit_comp.c:12: include/linux/dmaengine.h:973:1: error: expected identifier or '(' before '>>'

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/netdevice.h:38:0, from arch/x86/net/bpf_jit_comp.c:12: include/linux/dmaengine.h:973:1: error: expected identifier or '(' before ''

Re: linux-next: build failure after merge of the slave-dma tree

On Tue, Apr 02, 2013 at 12:57:11PM +1100, Stephen Rothwell wrote: Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/netdevice.h:38:0, from arch/x86/net/bpf_jit_comp.c:12:

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Jan 07, 2013 at 11:26:37AM +1100, Stephen Rothwell wrote: > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) failed like this: Hi Stephen, I rebased the tree last night and messed up at two places. Viresh helped to fix one. I have pushed the fixed tree

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Jan 07, 2013 at 11:26:37AM +1100, Stephen Rothwell wrote: After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: Hi Stephen, I rebased the tree last night and messed up at two places. Viresh helped to fix one. I have pushed the fixed tree now.

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/dmatest.c: In function 'unmap_dst': drivers/dma/dmatest.c:244:21: error: invalid storage class for function 'min_odd' drivers/dma/dmatest.c:244:1: warning: ISO C90 forbids

linux-next: build failure after merge of the slave-dma tree

Hi Vinod, After merging the slave-dma tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/dma/dmatest.c: In function 'unmap_dst': drivers/dma/dmatest.c:244:21: error: invalid storage class for function 'min_odd' drivers/dma/dmatest.c:244:1: warning: ISO C90 forbids