All of lore.kernel.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: dt changes for v4.2
Date: Thu, 18 Jun 2015 21:51:41 +0200	[thread overview]
Message-ID: <5583214D.6020205@free-electrons.com> (raw)

Hi,

Here is the third pull request for cleanup for mvebu for v4.2.
This pull request came very late, but as explained in the signed tag,
without it spi muxing will be broken in 4.2-rc1 for Armada XP.

Gregory

The following changes since commit 2d2959286017f5501187cfa47d3854f955c4beae:

  ARM: mvebu: use improved armada spi device tree compatible name for each SoC (2015-05-27 12:04:45 +0200)

are available in the git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-dt-4.2-3

for you to fetch changes up to 8c19a731a1a8b1f447a972174d2b2fe30d625518:

  ARM: mvebu: adjust Armada XP DT spi muxing after pinctrl function rename (2015-06-17 15:42:15 +0200)

----------------------------------------------------------------
mvebu dt changes for v4.2 (part #3)

Update Armada XP DT spi muxing after pinctrl function rename which was
merged in the pinctrl subsystem for 4.2. Without it the spi muxing
will be broken in 4.2-rc1 for Armada XP.

----------------------------------------------------------------
Thomas Petazzoni (1):
      ARM: mvebu: adjust Armada XP DT spi muxing after pinctrl function rename

 arch/arm/boot/dts/armada-xp.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2015-06-18 19:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 19:51 Gregory CLEMENT [this message]
2015-07-01 20:42 ` [GIT PULL] ARM: mvebu: dt changes for v4.2 Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2015-05-15 13:09 Gregory CLEMENT
2015-05-15 15:29 ` 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=5583214D.6020205@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.