linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christophe Kerello <christophe.kerello@st.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: linux-next: manual merge of the spi tree with the mtd tree
Date: Sun, 9 Aug 2020 18:49:19 +1000	[thread overview]
Message-ID: <20200809184919.2621b652@canb.auug.org.au> (raw)
In-Reply-To: <20200708143759.50246487@canb.auug.org.au>

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

Hi all,

On Wed, 8 Jul 2020 14:37:59 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the spi tree got conflicts in:
> 
>   drivers/memory/Kconfig
>   drivers/memory/Makefile
> 
> between commit:
> 
>   66b8173a197f ("memory: stm32-fmc2-ebi: add STM32 FMC2 EBI controller driver")
> 
> from the mtd tree and commit:
> 
>   ca7d8b980b67 ("memory: add Renesas RPC-IF driver")
> 
> from the spi 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.
> 
> 
> diff --cc drivers/memory/Kconfig
> index be69c07b8941,e438d79857da..000000000000
> --- a/drivers/memory/Kconfig
> +++ b/drivers/memory/Kconfig
> @@@ -174,16 -174,15 +174,25 @@@ config PL353_SM
>   	  This driver is for the ARM PL351/PL353 Static Memory
>   	  Controller(SMC) module.
>   
> + config RENESAS_RPCIF
> + 	tristate "Renesas RPC-IF driver"
> + 	depends on ARCH_RENESAS
> + 	select REGMAP_MMIO
> + 	help
> + 	  This supports Renesas R-Car Gen3 RPC-IF which provides either SPI
> + 	  host or HyperFlash. You'll have to select individual components
> + 	  under the corresponding menu.
> + 
>  +config STM32_FMC2_EBI
>  +	tristate "Support for FMC2 External Bus Interface on STM32MP SoCs"
>  +	depends on MACH_STM32MP157 || COMPILE_TEST
>  +	select MFD_SYSCON
>  +	help
>  +	  Select this option to enable the STM32 FMC2 External Bus Interface
>  +	  controller. This driver configures the transactions with external
>  +	  devices (like SRAM, ethernet adapters, FPGAs, LCD displays, ...) on
>  +	  SOCs containing the FMC2 External Bus Interface.
>  +
>   source "drivers/memory/samsung/Kconfig"
>   source "drivers/memory/tegra/Kconfig"
>   
> diff --cc drivers/memory/Makefile
> index d3d8d6ced342,d105f8ebe8b8..000000000000
> --- a/drivers/memory/Makefile
> +++ b/drivers/memory/Makefile
> @@@ -22,7 -22,7 +22,8 @@@ obj-$(CONFIG_JZ4780_NEMC)	+= jz4780-nem
>   obj-$(CONFIG_MTK_SMI)		+= mtk-smi.o
>   obj-$(CONFIG_DA8XX_DDRCTL)	+= da8xx-ddrctl.o
>   obj-$(CONFIG_PL353_SMC)		+= pl353-smc.o
> + obj-$(CONFIG_RENESAS_RPCIF)	+= renesas-rpc-if.o
>  +obj-$(CONFIG_STM32_FMC2_EBI)	+= stm32-fmc2-ebi.o
>   
>   obj-$(CONFIG_SAMSUNG_MC)	+= samsung/
>   obj-$(CONFIG_TEGRA_MC)		+= tegra/

This is now a conflict between the mtd tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

      reply	other threads:[~2020-08-09  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08  4:37 linux-next: manual merge of the spi tree with the mtd tree Stephen Rothwell
2020-08-09  8:49 ` Stephen Rothwell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200809184919.2621b652@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=broonie@kernel.org \
    --cc=christophe.kerello@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard.weinberger@gmail.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).