From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Third Round of Renesas ARM Based SoC Updates for v3.15
Date: Mon, 10 Mar 2014 17:36:55 +0900 [thread overview]
Message-ID: <cover.1394440471.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider this third round of Renesas ARM based SoC updates for v3.15.
I am sending this pull request after the release of v3.14-rc6
as it only includes a fix.
This pull request is based on the previous round of
such requests, tagged as renesas-soc2-for-v3.15,
which I have already sent a pull-request for.
The following changes since commit c4ca5d80e03559fd95c526ece5ce39fc732a2511:
ARM: shmobile: Move SYSC base variable to inside ifdefs (2014-02-26 14:53:35 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc3-for-v3.15
for you to fetch changes up to 56ff873122c4baab43df241c7701d043b8ec8a8e:
ARM: shmobile: APMU: Fix warnings due to improper printk formats (2014-03-06 13:14:03 +0900)
----------------------------------------------------------------
Third Round of Renesas ARM Based SoC Updates for v3.15
Fix warnings due to improper printk formats in shared APMU code.
----------------------------------------------------------------
Laurent Pinchart (1):
ARM: shmobile: APMU: Fix warnings due to improper printk formats
arch/arm/mach-shmobile/platsmp-apmu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
next reply other threads:[~2014-03-10 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 8:36 Simon Horman [this message]
2014-03-10 8:36 ` [PATCH] ARM: shmobile: APMU: Fix warnings due to improper printk formats Simon Horman
2014-03-17 7:50 ` [GIT PULL] Third Round of Renesas ARM Based SoC Updates for v3.15 Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2014-02-21 6:13 Simon Horman
2014-03-17 7:28 ` 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.1394440471.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).