From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] ARM: shmobile: Move SoC-specific header files
Date: Wed, 25 Jun 2014 17:00:00 +0900 [thread overview]
Message-ID: <20140625075959.GA10050@verge.net.au> (raw)
In-Reply-To: <1403283189-21688-1-git-send-email-geert+renesas@glider.be>
On Fri, Jun 20, 2014 at 06:53:00PM +0200, Geert Uytterhoeven wrote:
> It's Friday afternoon, hence the ideal time for a no-brainer patch
> series to move the shmobile SoC-specific header files, so they can be
> included as "<soc>.h" instead of the old style <mach/<soc>.h>.
>
> All build-tested. Multi-platform shmobile also boot-tested on
> r8a7791/koelsch.
>
> [1/9] ARM: shmobile: Move r7s72100.h
> [2/9] ARM: shmobile: Move r8a73a4.h
> [3/9] ARM: shmobile: Move r8a7740.h
> [4/9] ARM: shmobile: Move r8a7778.h
> [5/9] ARM: shmobile: Move r8a7779.h
> [6/9] ARM: shmobile: Move r8a7790.h
> [7/9] ARM: shmobile: Move r8a7791.h
> [8/9] ARM: shmobile: Move sh7372.h
> [9/9] ARM: shmobile: Move sh73a0.h
Thanks, I will queue these up.
prev parent reply other threads:[~2014-06-25 8:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 16:53 [PATCH 0/9] ARM: shmobile: Move SoC-specific header files Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 1/9] ARM: shmobile: Move r7s72100.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 2/9] ARM: shmobile: Move r8a73a4.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 3/9] ARM: shmobile: Move r8a7740.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 4/9] ARM: shmobile: Move r8a7778.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 5/9] ARM: shmobile: Move r8a7779.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 6/9] ARM: shmobile: Move r8a7790.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 7/9] ARM: shmobile: Move r8a7791.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 8/9] ARM: shmobile: Move sh7372.h Geert Uytterhoeven
2014-06-20 16:53 ` [PATCH 9/9] ARM: shmobile: Move sh73a0.h Geert Uytterhoeven
2014-06-25 8:00 ` Simon Horman [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=20140625075959.GA10050@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;
as well as URLs for NNTP newsgroup(s).