public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: soc for v4.11 (#2)
Date: Tue, 31 Jan 2017 15:14:27 +0100	[thread overview]
Message-ID: <87wpdbz58c.fsf@free-electrons.com> (raw)

Hi,

Here is the second pull request for soc for mvebu for v4.11.

I hope it is not too late, the support for this new SoC needed to have
several iteration and the last one was mainly cosmetic. The code was
in linux-next since last week by the way. SO I don't expect any
regression with it.

Thanks,

Gregory

The following changes since commit f2591b993ec95fd8d67c68187f07f30c9d79b38c:

  soc: dove: constify reset_control_ops structures (2017-01-27 17:52:57 +0100)

are available in the git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-soc-4.11-2

for you to fetch changes up to db88977894aba193deee70b335c3db58b7ac6393:

  arm: mvebu: support for SMP on 98DX3336 SoC (2017-01-30 14:40:56 +0100)

----------------------------------------------------------------
mvebu soc for 4.11 (part 2)

SoC part of the support for the for Marvell switches with integrated
CPUs based on Armada XP: the SMP support is slightly different.

----------------------------------------------------------------
Chris Packham (1):
      arm: mvebu: support for SMP on 98DX3336 SoC

 Documentation/devicetree/bindings/arm/cpus.txt     |  1 +
 .../bindings/arm/marvell/98dx3236-resume-ctrl.txt  | 16 +++++
 arch/arm/mach-mvebu/platsmp.c                      | 75 ++++++++++++++++++++++
 3 files changed, 92 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/marvell/98dx3236-resume-ctrl.txt

             reply	other threads:[~2017-01-31 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 14:14 Gregory CLEMENT [this message]
2017-02-07 15:17 ` [GIT PULL] ARM: mvebu: soc for v4.11 (#2) Arnd Bergmann

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=87wpdbz58c.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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