Skip to contentSkip to conversation

ARM: mvebu: arm64 for v4.6 (#1)

GIT PULL Applied Gregory CLEMENT 2 participants 4 messages Feb 17, 2016 – Feb 25, 2016

lore
Share & tools
lore
#0 lore raw

Hi,

Here is the first pull request for arm64 for mvebu for v4.6. It is even the first pull request ever for arm64 for us. Let me know if I am doing it wrong.

I split my initial series[1] in two parts: device tree related and non device tree related. I will also let the driver maintainers directly take the related patch for ATA and serial.

For this non device tree part I have a dependency with the irchip subsystem. For this I based on the irqchip/mvebu immutable branch form Jason Cooper located at git://git.infradead.org/users/jcooper/linux.git.

Thanks,

Gregory

[1]: https://lkml.org/lkml/2016/2/16/735

The following changes since commit 63131b636a0ec969e8b98122c1a928b5a2649d3b:

irqchip/armada-370-xp: Do not enable it by default when ARCH_MVEBU is selected (2016-02-16 18:11:39 +0000)

are available in the git repository at:

git://git.infradead.org/linux-mvebu.git tags/mvebu-arm64-4.6-1

for you to fetch changes up to e772ca05cceb1480bdc7a7579e042b18558d0959:

arm64: defconfig: enable Armada 3700 related config (2016-02-17 16:23:20 +0100)

----------------------------------------------------------------
mvebu arm64 for 4.6 (part 1)

Non dt part of the Armada 3700 support:
- Kconfig update
- defconfig update
- documentation update (including MAINTAINERS:)

----------------------------------------------------------------
Gregory CLEMENT (4):
arm64: add mvebu architecture entry
MAINTAINERS: Extend dts entry for ARM64 mvebu files
Documentation: arm: update supported Marvell EBU processors
arm64: defconfig: enable Armada 3700 related config

 Documentation/arm/Marvell/README | 13 +++++++++++++
 MAINTAINERS                      |  1 +
 arch/arm64/Kconfig.platforms     |  6 ++++++
 arch/arm64/configs/defconfig     |  5 +++++
 4 files changed, 25 insertions(+)
#1 lore raw
Quoted 16 lines · Gregory CLEMENT

Hi,

Here is the first pull request for arm64 for mvebu for v4.6. It is even the first pull request ever for arm64 for us. Let me know if I am doing it wrong.

I split my initial series[1] in two parts: device tree related and non device tree related. I will also let the driver maintainers directly take the related patch for ATA and serial.

For this non device tree part I have a dependency with the irchip subsystem. For this I based on the irqchip/mvebu immutable branch form Jason Cooper located at git://git.infradead.org/users/jcooper/linux.git.

Thanks,

Quoted 7 lines

Gregory

[1]: https://lkml.org/lkml/2016/2/16/735

The following changes since commit 63131b636a0ec969e8b98122c1a928b5a2649d3b:

irqchip/armada-370-xp: Do not enable it by default when ARCH_MVEBU is selected (2016-02-16 18:11:39 +0000)

PLease do this by explicit merge instead in the future, so it's obvious that there is an external branch merged in history later.

That way, doing the full diffstat including the merge is just fine too.

Quoted 7 lines

are available in the git repository at:

git://git.infradead.org/linux-mvebu.git tags/mvebu-arm64-4.6-1

for you to fetch changes up to e772ca05cceb1480bdc7a7579e042b18558d0959:

arm64: defconfig: enable Armada 3700 related config (2016-02-17 16:23:20 +0100)

Merged, thanks!

-Olof

#2 lore raw

Hi Olof,

Quoted 21 lines · Olof Johansson
Quoted 20 lines · Gregory CLEMENT

Hi,

Here is the first pull request for arm64 for mvebu for v4.6. It is even the first pull request ever for arm64 for us. Let me know if I am doing it wrong.

I split my initial series[1] in two parts: device tree related and non device tree related. I will also let the driver maintainers directly take the related patch for ATA and serial.

For this non device tree part I have a dependency with the irchip subsystem. For this I based on the irqchip/mvebu immutable branch form Jason Cooper located at git://git.infradead.org/users/jcooper/linux.git.

Thanks,

Gregory

[1]: https://lkml.org/lkml/2016/2/16/735

Quoted 8 lines
Quoted 3 lines

The following changes since commit 63131b636a0ec969e8b98122c1a928b5a2649d3b:

irqchip/armada-370-xp: Do not enable it by default when ARCH_MVEBU is selected (2016-02-16 18:11:39 +0000)

PLease do this by explicit merge instead in the future, so it's obvious that there is an external branch merged in history later.

That way, doing the full diffstat including the merge is just fine too.

Actually I did an explicite merge but my start commit for the pull request was the last commit of the merged branch. So if I undrestand well, I sould have used the v4.5-rc2 here as start commit.

Thanks,

Gregory

Quoted 14 lines
Quoted 9 lines

are available in the git repository at:

git://git.infradead.org/linux-mvebu.git tags/mvebu-arm64-4.6-1

for you to fetch changes up to e772ca05cceb1480bdc7a7579e042b18558d0959:

arm64: defconfig: enable Armada 3700 related config (2016-02-17 16:23:20 +0100)

Merged, thanks!

-Olof

Signature · 4 lines
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#3 lore raw
Quoted 29 lines · Gregory CLEMENT

Hi Olof,

Quoted 25 lines · Olof Johansson
Quoted 23 lines · Gregory CLEMENT

Hi,

Here is the first pull request for arm64 for mvebu for v4.6. It is even the first pull request ever for arm64 for us. Let me know if I am doing it wrong.

I split my initial series[1] in two parts: device tree related and non device tree related. I will also let the driver maintainers directly take the related patch for ATA and serial.

For this non device tree part I have a dependency with the irchip subsystem. For this I based on the irqchip/mvebu immutable branch form Jason Cooper located at git://git.infradead.org/users/jcooper/linux.git.

Thanks,

Gregory

[1]: https://lkml.org/lkml/2016/2/16/735

The following changes since commit 63131b636a0ec969e8b98122c1a928b5a2649d3b:

irqchip/armada-370-xp: Do not enable it by default when ARCH_MVEBU is selected (2016-02-16 18:11:39 +0000)

Quoted 8 lines
Quoted 4 lines

PLease do this by explicit merge instead in the future, so it's obvious that there is an external branch merged in history later.

That way, doing the full diffstat including the merge is just fine too.

Actually I did an explicite merge but my start commit for the pull request was the last commit of the merged branch. So if I undrestand well, I sould have used the v4.5-rc2 here as start commit.

Or use --no-ff so you get a merge commit instead of a fast-forward.

-Olof