[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20190222092513.6fc2a708@canb.auug.org.au>
Date: Fri, 22 Feb 2019 09:25:13 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
PowerPC <linuxppc-dev@...ts.ozlabs.org>,
Christoph Hellwig <hch@....de>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linux-next: manual merge of the powerpc tree with the dma-mapping
tree
Hi all,
Today's linux-next merge of the powerpc tree got a conflict in:
kernel/dma/Kconfig
between commits:
ff4c25f26a71 ("dma-mapping: improve selection of dma_declare_coherent availability")
from the dma-mapping tree and commit:
11ddce15451e ("dma-mapping, powerpc: simplify the arch dma_set_mask override")
from the powerpc tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc kernel/dma/Kconfig
index 212aac7c675f,0711d18645de..000000000000
--- a/kernel/dma/Kconfig
+++ b/kernel/dma/Kconfig
@@@ -16,13 -16,10 +16,16 @@@ config ARCH_DMA_ADDR_T_64BI
config ARCH_HAS_DMA_COHERENCE_H
bool
+ config ARCH_HAS_DMA_SET_MASK
+ bool
+
-config HAVE_GENERIC_DMA_COHERENT
+config DMA_DECLARE_COHERENT
+ bool
+
+config ARCH_HAS_SETUP_DMA_OPS
+ bool
+
+config ARCH_HAS_TEARDOWN_DMA_OPS
bool
config ARCH_HAS_SYNC_DMA_FOR_DEVICE
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists