From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Cleanup for v4.6
Date: Fri, 26 Feb 2016 22:39:08 +0100 [thread overview]
Message-ID: <3722431.YmSOxDWsdc@wuerfel> (raw)
In-Reply-To: <cover.1456275967.git.horms+renesas@verge.net.au>
On Wednesday 24 February 2016 10:20:50 Simon Horman wrote:
> Please consider these second round of Renesas ARM based SoC cleanups for v4.6.
>
> This pull request is based on "Renesas ARM Based SoC Fixes for v4.5",
> tagged as renesas-soc-fixes-for-v4.5, which I have already sent a
> pull-request for.
>
> The reason for that base is that the SCU cleanup depends on a change
> in the fixes pull request.
Pulled into next/cleanup, thanks!
Arnd
prev parent reply other threads:[~2016-02-26 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 1:20 [GIT PULL] Second Round of Renesas ARM Based SoC Cleanup for v4.6 Simon Horman
2016-02-24 1:21 ` [PATCH 1/2] ARM: shmobile: Consolidate SCU mapping code Simon Horman
2016-02-24 1:21 ` [PATCH 2/2] ARM: shmobile: Kconfig: Get rid of old comment Simon Horman
2016-02-26 21:39 ` Arnd Bergmann [this message]
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=3722431.YmSOxDWsdc@wuerfel \
--to=arnd@arndb.de \
--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).