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

Groups > linux.kernel > #1281639 > unrolled thread

linux-next: manual merge of the mvebu tree with the arm-soc tree

Back to article view | Back to linux.kernel

Contents

  linux-next: manual merge of the mvebu tree with the arm-soc tree Mark Brown <broonie@kernel.org> - 2015-12-02 12:20 +0100
    Re: linux-next: manual merge of the mvebu tree with the arm-soc tree Mark Brown <broonie@kernel.org> - 2015-12-02 12:20 +0100
      Re: linux-next: manual merge of the mvebu tree with the arm-soc tree Arnd Bergmann <arnd@arndb.de> - 2015-12-02 12:30 +0100
        Re: linux-next: manual merge of the mvebu tree with the arm-soc tree Gregory CLEMENT <gregory.clement@free-electrons.com> - 2015-12-02 15:00 +0100
          Re: linux-next: manual merge of the mvebu tree with the arm-soc tree Arnd Bergmann <arnd@arndb.de> - 2015-12-02 16:20 +0100

#1281639 — linux-next: manual merge of the mvebu tree with the arm-soc tree

[Multipart message — attachments visible in raw view] — view raw

Hi all,

Today's linux-next merge of the mvebu tree got a conflict in  between commit
377524dc4d77f50e ("ARM: mmp: move into ARCH_MULTIPLATFORM") from the arm-soc
tree and commit 5f4423af9dd17 ("ARM: orion: multiplatform support") from the
mvebu tree.

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

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 5a328472bd8c..882f5f33bc7d 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -490,46 +490,6 @@ config ARCH_IXP4XX
 	help
 	  Support for Intel's IXP4XX (XScale) family of processors.
 
-config ARCH_DOVE
-	bool "Marvell Dove"
-	select ARCH_REQUIRE_GPIOLIB
-	select CPU_PJ4
-	select GENERIC_CLOCKEVENTS
-	select MIGHT_HAVE_PCI
-	select MVEBU_MBUS
-	select PINCTRL
-	select PINCTRL_DOVE
-	select PLAT_ORION_LEGACY
-	help
-	  Support for the Marvell Dove SoC 88AP510
-
-config ARCH_MV78XX0
-	bool "Marvell MV78xx0"
-	select ARCH_REQUIRE_GPIOLIB
-	select CPU_FEROCEON
-	select GENERIC_CLOCKEVENTS
-	select MVEBU_MBUS
-	select PCI
-	select PLAT_ORION_LEGACY
-	help
-	  Support for the following Marvell MV78xx0 series SoCs:
-	  MV781x0, MV782x0.
-
-config ARCH_ORION5X
-	bool "Marvell Orion"
-	depends on MMU
-	select ARCH_REQUIRE_GPIOLIB
-	select CPU_FEROCEON
-	select GENERIC_CLOCKEVENTS
-	select MVEBU_MBUS
-	select PCI
-	select PLAT_ORION_LEGACY
-	select MULTI_IRQ_HANDLER
-	help
-	  Support for the following Marvell Orion 5x series SoCs:
-	  Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
-	  Orion-2 (5281), Orion-1-90 (6183).
-
 config ARCH_KS8695
 	bool "Micrel/Kendin KS8695"
 	select ARCH_REQUIRE_GPIOLIB

[toc] | [next] | [standalone]

#1281640

[Multipart message — attachments visible in raw view] — view raw

On Wed, Dec 02, 2015 at 11:12:44AM +0000, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the mvebu tree got a conflict in  between commit
> 377524dc4d77f50e ("ARM: mmp: move into ARCH_MULTIPLATFORM") from the arm-soc
> tree and commit 5f4423af9dd17 ("ARM: orion: multiplatform support") from the
> mvebu tree.

Ccing in Arnd since I forgot to do that.

> 
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 5a328472bd8c..882f5f33bc7d 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -490,46 +490,6 @@ config ARCH_IXP4XX
>  	help
>  	  Support for Intel's IXP4XX (XScale) family of processors.
>  
> -config ARCH_DOVE
> -	bool "Marvell Dove"
> -	select ARCH_REQUIRE_GPIOLIB
> -	select CPU_PJ4
> -	select GENERIC_CLOCKEVENTS
> -	select MIGHT_HAVE_PCI
> -	select MVEBU_MBUS
> -	select PINCTRL
> -	select PINCTRL_DOVE
> -	select PLAT_ORION_LEGACY
> -	help
> -	  Support for the Marvell Dove SoC 88AP510
> -
> -config ARCH_MV78XX0
> -	bool "Marvell MV78xx0"
> -	select ARCH_REQUIRE_GPIOLIB
> -	select CPU_FEROCEON
> -	select GENERIC_CLOCKEVENTS
> -	select MVEBU_MBUS
> -	select PCI
> -	select PLAT_ORION_LEGACY
> -	help
> -	  Support for the following Marvell MV78xx0 series SoCs:
> -	  MV781x0, MV782x0.
> -
> -config ARCH_ORION5X
> -	bool "Marvell Orion"
> -	depends on MMU
> -	select ARCH_REQUIRE_GPIOLIB
> -	select CPU_FEROCEON
> -	select GENERIC_CLOCKEVENTS
> -	select MVEBU_MBUS
> -	select PCI
> -	select PLAT_ORION_LEGACY
> -	select MULTI_IRQ_HANDLER
> -	help
> -	  Support for the following Marvell Orion 5x series SoCs:
> -	  Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
> -	  Orion-2 (5281), Orion-1-90 (6183).
> -
>  config ARCH_KS8695
>  	bool "Micrel/Kendin KS8695"
>  	select ARCH_REQUIRE_GPIOLIB

[toc] | [prev] | [next] | [standalone]

#1281670

On Wednesday 02 December 2015 11:18:29 Mark Brown wrote:
> On Wed, Dec 02, 2015 at 11:12:44AM +0000, Mark Brown wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the mvebu tree got a conflict in  between commit
> > 377524dc4d77f50e ("ARM: mmp: move into ARCH_MULTIPLATFORM") from the arm-soc
> > tree and commit 5f4423af9dd17 ("ARM: orion: multiplatform support") from the
> > mvebu tree.
> 
> Ccing in Arnd since I forgot to do that.
> 

I was planning to merge all the multiplatform changes into one next/multiplatform
branch, but the mvebu maintainers preferred to keep this one in their tree at
least initially. The conflict will go away once it's tested sufficiently and
I'm pulling it back.
	
	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1281809

Hi Arnd,
 
 On mer., déc. 02 2015, Arnd Bergmann <arnd@arndb.de> wrote:

> On Wednesday 02 December 2015 11:18:29 Mark Brown wrote:
>> On Wed, Dec 02, 2015 at 11:12:44AM +0000, Mark Brown wrote:
>> > Hi all,
>> > 
>> > Today's linux-next merge of the mvebu tree got a conflict in  between commit
>> > 377524dc4d77f50e ("ARM: mmp: move into ARCH_MULTIPLATFORM") from the arm-soc
>> > tree and commit 5f4423af9dd17 ("ARM: orion: multiplatform support") from the
>> > mvebu tree.
>> 
>> Ccing in Arnd since I forgot to do that.
>> 
>
> I was planning to merge all the multiplatform changes into one next/multiplatform
> branch, but the mvebu maintainers preferred to keep this one in their
> tree at

Indeed except the arch/arm/Kconfig file all the other files belong to
the mbebu subsystem and it is easier to to keep in our tree to handle them.

> least initially. The conflict will go away once it's tested sufficiently and
> I'm pulling it back.

By the way, when you will pull our tree, we will still have it our own
mvebu/for-next branch. Will git managed to automagically resolve the
conflict by getting the resolution you will do in your branch?

A another solution could be to have a separate patch for the
arch/arm/Kconfig file that you keep in arm-soc.

Grégory

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1281896

On Wednesday 02 December 2015 14:49:52 Gregory CLEMENT wrote:
> 
> > least initially. The conflict will go away once it's tested sufficiently and
> > I'm pulling it back.
> 
> By the way, when you will pull our tree, we will still have it our own
> mvebu/for-next branch. Will git managed to automagically resolve the
> conflict by getting the resolution you will do in your branch?

Yes, that should be fine, unless you resolve the same conflict differently.

> A another solution could be to have a separate patch for the
> arch/arm/Kconfig file that you keep in arm-soc.

No, I don't think that will be necessary.

	Arnd 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web