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

2019-07-07 Thread Robin Gong
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 i

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

2019-07-07 Thread Robin Gong
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. > > https://eur01.safelinks.pr

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

2019-07-07 Thread Vinod Koul
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. > > https://patchwork.kernel.or

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

2019-07-07 Thread Vinod Koul
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. > > > https://eur01.safelinks.protection.outlook.com/?url

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

2019-07-07 Thread zhangfei
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 mi

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

2019-07-07 Thread Robin Gong
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 > > > hwork.kernel.org%2Fp

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

2019-07-07 Thread Robin Gong
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

2019-07-06 Thread Vinod Koul
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 does

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

2019-07-06 Thread Robin Gong
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

2018-10-03 Thread Vinod
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 fil

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

2017-08-22 Thread Vinod Koul
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: > d

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

2016-09-19 Thread Vinod Koul
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 in

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

2016-09-16 Thread Peter Griffin
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], fixes

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

2015-10-15 Thread Stephen Rothwell
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

2015-10-15 Thread Arnd Bergmann
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 mer

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

2015-10-14 Thread Stephen Rothwell
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 onl

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

2015-10-14 Thread Koul, Vinod
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 > #incl

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

2015-08-24 Thread Maxime Ripard
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 > > > t

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

2015-08-24 Thread Vinod Koul
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 th

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

2015-08-23 Thread Maxime Ripard
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

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

2015-08-05 Thread Vinod Koul
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 a

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

2015-02-15 Thread Vinod Koul
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 l

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

2015-02-15 Thread Yibin Gong
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: > > drivers/dma/i

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

2014-12-08 Thread Vinod Koul
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 :) Fen

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

2014-11-12 Thread Ludovic Desroches
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

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

2014-11-09 Thread Vinod Koul
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 declara

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

2014-09-15 Thread Geert Uytterhoeven
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 = 5000

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

2014-07-28 Thread Maxime Ripard
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 fun

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

2014-07-28 Thread Vinod Koul
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: impli

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

2013-04-01 Thread Vinod Koul
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

2013-01-07 Thread Vinod Koul
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