linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: build failure after merge of the slave-dma tree
@ 2015-08-06  2:22 Stephen Rothwell
  2015-08-06  3:00 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2015-08-06  2:22 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Maxime Ripard, Cyrille Pitchen

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 commit

  25fed8c2fff1 ("dmaengine: hdmac: Add memset capabilities")

interacting with commit

  93dce3a6434f ("dmaengine: at_hdmac: fix residue computation")

>From Linus' tree (v4.2-rc5).  This should have been fixed up in commit

  fa362949e874 ("Merge branch 'for-linus' into next")

I have used the slave-dma tree from next-20150805 for today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2019-07-04  7:31 Stephen Rothwell
  2019-07-06 13:43 ` Robin Gong
  2019-07-08  1:22 ` Robin Gong
  0 siblings, 2 replies; 49+ messages in thread
From: Stephen Rothwell @ 2019-07-04  7:31 UTC (permalink / raw)
  To: Vinod Koul
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Robin Gong,
	Angelo Dureghello

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

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 today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2018-10-04  5:44 Stephen Rothwell
  2018-10-04  6:13 ` Vinod
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2018-10-04  5:44 UTC (permalink / raw)
  To: Vinod Koul
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Angelo Dureghello

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

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:
drivers/dma/fsl-edma-common.h:21: note: this is the location of the previous definition
 #define EDMA_SEEI_SEEI(x) ((x) & GENMASK(4, 0))

 ...

drivers/dma/fsl-edma.c:115:6: error: nested redefinition of 'enum fsl_edma_pm_state'
 enum fsl_edma_pm_state {
      ^~~~~~~~~~~~~~~~~
drivers/dma/fsl-edma.c:115:6: error: redeclaration of 'enum fsl_edma_pm_state'
In file included from drivers/dma/fsl-edma.c:25:
drivers/dma/fsl-edma-common.h:63:6: note: originally defined here
 enum fsl_edma_pm_state {
      ^~~~~~~~~~~~~~~~~

and so on ...

Caused by commit

  101d256a45ed ("Merge branch 'testing/dirn_remove' into next")

which reintroduced a whole lot of stuff into drivers/dma/fsl-edma.c that
had been modev out in commit

  9d831528a656 ("dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)")

I used the slave-dma tree from next-20181003 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2017-08-22  5:36 Stephen Rothwell
  2017-08-22 16:39 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2017-08-22  5:36 UTC (permalink / raw)
  To: Vinod Koul
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Stefan Roese,
	Dave Jiang

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':
drivers/dma/altera-msgdma.c:946:14: error: 'DMA_SG' undeclared (first use in this function)
  dma_cap_set(DMA_SG, dma_dev->cap_mask);
              ^
include/linux/dmaengine.h:1197:46: note: in definition of macro 'dma_cap_set'
 #define dma_cap_set(tx, mask) __dma_cap_set((tx), &(mask))
                                              ^
drivers/dma/altera-msgdma.c:946:14: note: each undeclared identifier is reported only once for each function it appears in
  dma_cap_set(DMA_SG, dma_dev->cap_mask);
              ^
include/linux/dmaengine.h:1197:46: note: in definition of macro 'dma_cap_set'
 #define dma_cap_set(tx, mask) __dma_cap_set((tx), &(mask))
                                              ^
drivers/dma/altera-msgdma.c:965:9: error: 'struct dma_device' has no member named 'device_prep_dma_sg'
  dma_dev->device_prep_dma_sg = msgdma_prep_sg;
         ^

Caused by commit

  a85c6f1b2921 ("dmaengine: Add driver for Altera / Intel mSGDMA IP core")

interacting with commit

  c678fa66341c ("dmaengine: remove DMA_SG as it is dead code in kernel")

This should have been fixed up in the merge commit

  0a0ab6497093 ("Merge branch 'topic/dmatest' into next")

I have used the slave-dma tree from next-20170817 for today.

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2016-09-16  3:18 Stephen Rothwell
  2016-09-16  8:34 ` Peter Griffin
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2016-09-16  3:18 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Peter Griffin

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 limitations"
drivers/video/fbdev/Kconfig:5:  symbol FB is selected by DRM_KMS_FB_HELPER
drivers/gpu/drm/Kconfig:42:     symbol DRM_KMS_FB_HELPER depends on DRM_KMS_HELPER
drivers/gpu/drm/Kconfig:36:     symbol DRM_KMS_HELPER is selected by DRM_VIRTIO_GPU
drivers/gpu/drm/virtio/Kconfig:1:       symbol DRM_VIRTIO_GPU depends on VIRTIO
drivers/virtio/Kconfig:1:       symbol VIRTIO is selected by REMOTEPROC
drivers/remoteproc/Kconfig:4:   symbol REMOTEPROC is selected by ST_SLIM_REMOTEPROC
drivers/remoteproc/Kconfig:103: symbol ST_SLIM_REMOTEPROC is selected by ST_FDMA
drivers/dma/Kconfig:440:        symbol ST_FDMA depends on DMADEVICES
drivers/dma/Kconfig:5:  symbol DMADEVICES is selected by SND_SOC_SH4_SIU
sound/soc/sh/Kconfig:29:        symbol SND_SOC_SH4_SIU is selected by SND_SIU_MIGOR
sound/soc/sh/Kconfig:58:        symbol SND_SIU_MIGOR depends on I2C
drivers/i2c/Kconfig:7:  symbol I2C is selected by FB_DDC
drivers/video/fbdev/Kconfig:63: symbol FB_DDC is selected by FB_CYBER2000_DDC
drivers/video/fbdev/Kconfig:382:        symbol FB_CYBER2000_DDC depends on FB_CYBER2000
drivers/video/fbdev/Kconfig:370:        symbol FB_CYBER2000 depends on FB
*
* Restart config...
*
*
* USB HID Boot Protocol drivers
*
USB HIDBP Keyboard (simple Boot) support (USB_KBD) [N/m/y/?] (NEW) aborted!

Console input/output is redirected. Run 'make oldconfig' to update configuration.

/home/sfr/next/next/scripts/kconfig/Makefile:37: recipe for target 'silentoldconfig' failed

Probably caused by commits

  73f19dcade3d ("remoteproc: st_slim_rproc: add a slimcore rproc driver")
  e0cbdfc766bf ("dmaengine: st_fdma: Add STMicroelectronics FDMA engine driver support")
  a490790f8df3 ("ARM: multi_v7_defconfig: Enable STi and simple-card drivers.")

I have used the slave-dma tree from next-20160915 for today.

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2015-10-15  0:51 Stephen Rothwell
  2015-10-15  3:35 ` Koul, Vinod
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2015-10-15  0:51 UTC (permalink / raw)
  To: Vinod Koul, Arnd Bergmann
  Cc: linux-next, linux-kernel, Christoph Hellwig, Andy Shevchenko

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 <asm-generic/io-64-nonatomic-lo-hi.h>
                                               ^

Caused by commit

  97c37accd38f ("dmaengine: idma64: use lo_hi_readq() / lo_hi_writeq()")

interacting with commit

  f626fe17485b ("move io-64-nonatomic*.h out of asm-generic")

from the asm-generic tree.

I have applied the folling merge fix patch and can carry it as necessary.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 15 Oct 2015 11:47:07 +1100
Subject: [PATCH] dmaengine: idma64: merge fix for "move io-64-nonatomic*.h out of asm-generic"

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/dma/idma64.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/dma/idma64.h b/drivers/dma/idma64.h
index f6aeff0af8a5..801d5462d663 100644
--- a/drivers/dma/idma64.h
+++ b/drivers/dma/idma64.h
@@ -15,8 +15,7 @@
 #include <linux/io.h>
 #include <linux/spinlock.h>
 #include <linux/types.h>
-
-#include <asm-generic/io-64-nonatomic-lo-hi.h>
+#include <linux/io-64-nonatomic-lo-hi.h>
 
 #include "virt-dma.h"
 
-- 
2.5.1

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

^ permalink raw reply related	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2015-02-16  1:09 Stephen Rothwell
  2015-02-16  1:48 ` Yibin Gong
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2015-02-16  1:09 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Robin Gong, Sascha Hauer

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2014-12-09  3:48 Stephen Rothwell
  2014-12-09  4:47 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2014-12-09  3:48 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Maxime Ripard, Laurent Pinchart

[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]

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'
   as->dma.chan_rx->device->device_control(as->dma.chan_rx,
                          ^
drivers/spi/spi-atmel.c:486:8: error: 'DMA_TERMINATE_ALL' undeclared (first use in this function)
        DMA_TERMINATE_ALL, 0);
        ^
drivers/spi/spi-atmel.c:486:8: note: each undeclared identifier is reported only once for each function it appears in
drivers/spi/spi-atmel.c:488:26: error: 'struct dma_device' has no member named 'device_control'
   as->dma.chan_tx->device->device_control(as->dma.chan_tx,
                          ^
drivers/usb/musb/ux500_dma.c: In function 'ux500_configure_channel':
drivers/usb/musb/ux500_dma.c:124:18: error: 'struct dma_device' has no member named 'device_control'
  dma_chan->device->device_control(dma_chan, DMA_SLAVE_CONFIG,
                  ^
drivers/usb/musb/ux500_dma.c:124:45: error: 'DMA_SLAVE_CONFIG' undeclared (first use in this function)
  dma_chan->device->device_control(dma_chan, DMA_SLAVE_CONFIG,
                                             ^
drivers/usb/musb/ux500_dma.c:124:45: note: each undeclared identifier is reported only once for each function it appears in
drivers/usb/musb/ux500_dma.c: In function 'ux500_dma_channel_abort':
drivers/usb/musb/ux500_dma.c:249:34: error: 'struct dma_device' has no member named 'device_control'
   ux500_channel->dma_chan->device->
                                  ^
drivers/usb/musb/ux500_dma.c:251:6: error: 'DMA_TERMINATE_ALL' undeclared (first use in this function)
      DMA_TERMINATE_ALL, 0);
      ^

Caused by commit f86999789afe ("dmaengine: Remove device_control and
device_slave_caps").

I have used the slave-dma tree from next-20141208 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2014-11-10  0:58 Stephen Rothwell
  2014-11-10  5:06 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2014-11-10  0:58 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Ludovic Desroches, Nicolas Ferre

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

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]
  at_xdmac_write(atxdmac, AT_XDMAC_GD, -1L);
  ^

Caused by commit e1f7c9eee707 ("dmaengine: at_xdmac: creation of the
atmel eXtended DMA Controller driver").

Also, lots of warnings like:

drivers/dma/at_xdmac.c: In function 'at_xdmac_prep_slave_sg':
include/linux/dynamic_debug.h:64:16: warning: format '%x' expects argument of type 'unsigned int', but argument 5 has type 'dma_addr_t' [-Wformat=]
  static struct _ddebug  __aligned(8)   \
                ^
include/linux/dynamic_debug.h:84:2: note: in expansion of macro 'DEFINE_DYNAMIC_DEBUG_METADATA'
  DEFINE_DYNAMIC_DEBUG_METADATA(descriptor, fmt);  \
  ^
include/linux/device.h:1107:2: note: in expansion of macro 'dynamic_dev_dbg'
  dynamic_dev_dbg(dev, format, ##__VA_ARGS__); \
  ^
drivers/dma/at_xdmac.c:621:3: note: in expansion of macro 'dev_dbg'
   dev_dbg(chan2dev(chan),
   ^

I have used the slave-dma tree from next-20141106 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2014-09-12  3:17 Stephen Rothwell
  2014-09-15  9:51 ` Geert Uytterhoeven
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2014-09-12  3:17 UTC (permalink / raw)
  To: Vinod Koul
  Cc: linux-next, linux-kernel, Mika Westerberg, Andy Shevchenko, Mark Brown

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

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 = 50000000,
   ^

Caused by commit bfe607a528ba ("spi/pxa2xx-pci: Add support for Intel
Braswell").

I have used the slave-dma tree from next-20140911 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2014-07-28  2:18 Stephen Rothwell
  2014-07-28  7:16 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2014-07-28  2:18 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Maxime Ripard

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

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' [-Werror=implicit-function-declaration]
  phys_addr_t reg = __virt_to_phys((unsigned long)pchan->base);
  ^

Caused by commit 555859308723 ("dmaengine: sun6i: Add driver for the
Allwinner A31 DMA controller").  Presumably missing an include file.

I have used the slave-dma tree from next-20140725 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2013-04-02  1:57 Stephen Rothwell
  2013-04-02  1:38 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2013-04-02  1:57 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

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 '>>' token

And many, many more :-(

Caused by commit 896b29f155cf ("Merge branch 'for-linus' into next").

Please at least build test your tree *before* publishing it :-(

I have used the slave-dma tree from next-20130328 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2013-01-07  0:26 Stephen Rothwell
  2013-01-07 14:00 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2013-01-07  0:26 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Akinobu Mita

[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]

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 mixed declarations and code [-Wdeclaration-after-statement]
drivers/dma/dmatest.c:265:12: error: invalid storage class for function 'dmatest_func'
drivers/dma/dmatest.c:550:13: error: invalid storage class for function 'dmatest_cleanup_channel'
drivers/dma/dmatest.c:570:12: error: invalid storage class for function 'dmatest_add_threads'
drivers/dma/dmatest.c:614:12: error: invalid storage class for function 'dmatest_add_channel'
drivers/dma/dmatest.c:652:13: error: invalid storage class for function 'filter'
drivers/dma/dmatest.c:660:19: error: invalid storage class for function 'dmatest_init'
drivers/dma/dmatest.c:685:1: error: invalid storage class for function '__inittest'
drivers/dma/dmatest.c:685:1: warning: 'alias' attribute ignored [-Wattributes]
drivers/dma/dmatest.c:687:20: error: invalid storage class for function 'dmatest_exit'
drivers/dma/dmatest.c:687:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
drivers/dma/dmatest.c:701:1: error: invalid storage class for function '__exittest'
drivers/dma/dmatest.c:701:1: warning: 'alias' attribute ignored [-Wattributes]
drivers/dma/dmatest.c:703:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
drivers/dma/dmatest.c:704:1: error: expected declaration or statement at end of input

Caused by commit 98edb45b7ba0 ("dmatest: adjust invalid module parameters
for number of source buffers").   You build tested this, right?

I have used the slave-dma tree from next-20130104 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2012-06-22  3:00 Stephen Rothwell
  2012-06-22  5:01 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2012-06-22  3:00 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Zhangfei Gao, Leo Yan, Qiao Zhou

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

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.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread
* linux-next: build failure after merge of the slave-dma tree
@ 2012-03-27  0:52 Stephen Rothwell
  2012-03-27  8:33 ` Vinod Koul
  0 siblings, 1 reply; 49+ messages in thread
From: Stephen Rothwell @ 2012-03-27  0:52 UTC (permalink / raw)
  To: Vinod Koul; +Cc: linux-next, linux-kernel, Javier Martin, Sascha Hauer

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

Hi Vinod,

After merging the slave-dma tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/dma/imx-dma.c:31:22: fatal error: mach/dma.h: No such file or directory

Caused by commit 6bd081277ea0 ("dmaengine: imx-dma: merge old dma-v1.c
with imx-dma.c").

I have used the slave-dma tree from next-20120326 for today.

I was wondering why this new work appeared during the merge window ...
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 49+ messages in thread

end of thread, other threads:[~2019-07-08  4:54 UTC | newest]

Thread overview: 49+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-06  2:22 linux-next: build failure after merge of the slave-dma tree 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
  -- 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-02-16  1:09 Stephen Rothwell
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-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

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).