linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Boards Updates for v3.16
Date: Wed, 14 May 2014 16:26:55 +0900	[thread overview]
Message-ID: <cover.1400052350.git.horms+renesas@verge.net.au> (raw)

Hi Olof, Hi Kevin, Hi Arnd,

Please consider these second round of
Renesas ARM based SoC boards updates for v3.16.

This pull request is based on the previous round of
such requests, tagged as renesas-boards-for-v3.16,
which you have previously pulled.


The following changes since commit a09b2f0ba170dc89a67d6c4c4f027b37a085dad9:

  ARM: shmobile: lager legacy: Enable Quad SPI transfers for the SPI FLASH (2014-04-15 08:13:22 +0900)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-boards2-for-v3.16

for you to fetch changes up to fd105ecf17fe459d979f336a7389d87172a1cf6d:

  ARM: shmobile: Minor cleanup of the Armadillo legacy board code (2014-05-11 20:59:57 +0900)

----------------------------------------------------------------
Second Round of Renesas ARM Based SoC Boards Updates for v3.16

r8a7740 (R-Mobile A1) based Armadillo800 EVA board
* Minor cleanup of the Armadillo legacy board code

----------------------------------------------------------------
Magnus Damm (1):
      ARM: shmobile: Minor cleanup of the Armadillo legacy board code

 arch/arm/mach-shmobile/board-armadillo800eva.c | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

             reply	other threads:[~2014-05-14  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14  7:26 Simon Horman [this message]
2014-05-14  7:26 ` [PATCH] ARM: shmobile: Minor cleanup of the Armadillo legacy board code Simon Horman
2014-05-20  5:39 ` [GIT PULL] Second Round of Renesas ARM Based SoC Boards Updates for v3.16 Olof Johansson

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=cover.1400052350.git.horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --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;
as well as URLs for NNTP newsgroup(s).