The patch titled
Subject: drivers/fpga/Kconfig: fix build failure
has been added to the -mm tree. Its filename is
fpga-zynq-fpga-fix-build-failure.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/fpga-zynq-fpga-fix-build-failure.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/fpga-zynq-fpga-fix-build-failure.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
Subject: drivers/fpga/Kconfig: fix build failure
While building m32r allmodconfig the build is failing with the error:
ERROR: "bad_dma_ops" [drivers/fpga/zynq-fpga.ko] undefined!
Xilinx Zynq FPGA is using DMA but there was no dependency while
building.
Link: http://lkml.kernel.org/r/1464346526-13913-1-git-send-email-sudipm.mukherjee@xxxxxxxxx
Signed-off-by: Sudip Mukherjee <sudip.mukherjee@xxxxxxxxxxxxxxx>
Cc: Alan Tull <atull@xxxxxxxxxxxxxxxxxxxxx>
Cc: Moritz Fischer <moritz.fischer@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/fpga/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff -puN drivers/fpga/Kconfig~fpga-zynq-fpga-fix-build-failure drivers/fpga/Kconfig
--- a/drivers/fpga/Kconfig~fpga-zynq-fpga-fix-build-failure
+++ a/drivers/fpga/Kconfig
@@ -21,6 +21,7 @@ config FPGA_MGR_SOCFPGA
config FPGA_MGR_ZYNQ_FPGA
tristate "Xilinx Zynq FPGA"
+ depends on HAS_DMA
help
FPGA manager driver support for Xilinx Zynq FPGAs.
_
Patches currently in -mm which might be from sudipm.mukherjee@xxxxxxxxx are
fpga-zynq-fpga-fix-build-failure.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
