From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM-based SoC fixes for v3.7 #2
Date: Fri, 19 Oct 2012 15:50:08 +0900 [thread overview]
Message-ID: <20121019065008.GA27867@verge.net.au> (raw)
In-Reply-To: <1350629360-27438-1-git-send-email-horms@verge.net.au>
On Fri, Oct 19, 2012 at 03:49:19PM +0900, Simon Horman wrote:
> Hi Olof, Hi Arnd,
>
> please consider the following fix for the r8a7779 SoC for 3.6.
Same typo as last time: s/3.6/3.7/
> It resolves some more fallout from recent IOMEM() changes.
>
> ----------------------------------------------------------------
> The following changes since commit 11f93576b0b50bf391ffafa544b85e541f5e59a5:
>
> ARM: shmobile: r8a7779: use __iomem pointers for MMIO (2012-10-16 08:58:56 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git fixes
>
> for you to fetch changes up to ed7d132a634e7e4c3fa657363df5df39e7f768e4:
>
> ARM: shmobile: r8a7779: I/O address abuse cleanup (2012-10-19 15:39:38 +0900)
>
> ----------------------------------------------------------------
> Kuninori Morimoto (1):
> ARM: shmobile: r8a7779: I/O address abuse cleanup
>
> arch/arm/mach-shmobile/setup-r8a7779.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-10-19 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 6:49 [GIT PULL] Renesas ARM-based SoC fixes for v3.7 #2 Simon Horman
2012-10-19 6:49 ` [PATCH] ARM: shmobile: r8a7779: I/O address abuse cleanup Simon Horman
2012-10-19 6:50 ` Simon Horman [this message]
2012-10-26 13:13 ` [GIT PULL] Renesas ARM-based SoC fixes for v3.7 #2 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=20121019065008.GA27867@verge.net.au \
--to=horms@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