Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1345475

linux-next: manual merge of the iommu tree with the samsung-krzk tree

Show all headers | View raw

Hi Joerg,

Today's linux-next merge of the iommu tree got a conflict in:

  drivers/memory/Kconfig

between commit:

  78fbb9361ca3 ("memory: Add support for Exynos SROM driver")

from the samsung-krzk tree and commit:

  cc8bbe1a8312 ("memory: mediatek: Add SMI driver")

from the iommu tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/memory/Kconfig
index bcb19822968b,51d5cd20c26a..000000000000
--- a/drivers/memory/Kconfig
+++ b/drivers/memory/Kconfig
@@@ -114,7 -114,14 +114,15 @@@ config JZ4780_NEM
  	  the Ingenic JZ4780. This controller is used to handle external
  	  memory devices such as NAND and SRAM.
  
+ config MTK_SMI
+ 	bool
+ 	depends on ARCH_MEDIATEK || COMPILE_TEST
+ 	help
+ 	  This driver is for the Memory Controller module in MediaTek SoCs,
+ 	  mainly help enable/disable iommu and control the power domain and
+ 	  clocks for each local arbiter.
+ 
 +source "drivers/memory/samsung/Kconfig"
  source "drivers/memory/tegra/Kconfig"
  
  endif

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

linux-next: manual merge of the iommu tree with the samsung-krzk  tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-02-29 05:30 +0100
  Re: linux-next: manual merge of the iommu tree with the samsung-krzk  tree Joerg Roedel <joro@8bytes.org> - 2016-02-29 09:00 +0100

csiph-web