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] Second Round of Renesas ARM based SoC fixes for v3.12
Date: Thu,  1 Aug 2013 17:27:15 +0900	[thread overview]
Message-ID: <cover.1375345067.git.horms+renesas@verge.net.au> (raw)

Hi Olof, Hi Arnd,

please consider this second round of Renesas ARM based SoC fixes for v3.12.

It is based on the first round of Renesas ARM based SoC fixes for v3.12,
/renesas-fixes-for-v3.12, which I have already send a pull-request for.

The following changes since commit 93d8a6fbe69a629a7bb37bb546699a5c49963dc5:

  ARM: shmobile: r8a7740: Fix TPU clock name (2013-07-19 11:12:35 +0900)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-fixes2-for-v3.12

for you to fetch changes up to ab40900b70dc31a64f23b1b4dbb0917afb039775:

  ARM: shmobile: armadillo800eva-reference: fix compiler warning (2013-07-23 10:35:33 +0900)

----------------------------------------------------------------
Second Round of Renesas ARM based SoC fixes for v3.12

* Fix compiler warning in armadillo800eva board code

----------------------------------------------------------------
Guennadi Liakhovetski (1):
      ARM: shmobile: armadillo800eva-reference: fix compiler warning

 arch/arm/mach-shmobile/board-armadillo800eva-reference.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

             reply	other threads:[~2013-08-01  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  8:27 Simon Horman [this message]
2013-08-01  8:27 ` [PATCH] ARM: shmobile: armadillo800eva-reference: fix compiler warning Simon Horman
2013-08-14  8:00 ` [GIT] Second Round of Renesas ARM based SoC fixes for v3.12 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.1375345067.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).