From: Magnus Damm <magnus.damm@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 09/12] ARM: shmobile: Rework include path for r8a7791
Date: Mon, 24 Feb 2014 05:42:23 +0000 [thread overview]
Message-ID: <20140224054223.1143.82115.sendpatchset@w520> (raw)
In-Reply-To: <20140224054058.1143.14096.sendpatchset@w520>
From: Magnus Damm <damm@opensource.se>
Convert r8a7791 SoC code use of include files from
the style <mach/something.h> to "something.h".
Signed-off-by: Magnus Damm <damm@opensource.se>
---
arch/arm/mach-shmobile/clock-r8a7791.c | 4 ++--
arch/arm/mach-shmobile/setup-r8a7791.c | 8 ++++----
arch/arm/mach-shmobile/smp-r8a7791.c | 4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
--- 0001/arch/arm/mach-shmobile/clock-r8a7791.c
+++ work/arch/arm/mach-shmobile/clock-r8a7791.c 2014-02-24 13:49:45.000000000 +0900
@@ -23,8 +23,8 @@
#include <linux/kernel.h>
#include <linux/sh_clk.h>
#include <linux/clkdev.h>
-#include <mach/clock.h>
-#include <mach/common.h>
+#include "clock.h"
+#include "common.h"
/*
* MD EXTAL PLL0 PLL1 PLL3
--- 0001/arch/arm/mach-shmobile/setup-r8a7791.c
+++ work/arch/arm/mach-shmobile/setup-r8a7791.c 2014-02-24 13:49:04.000000000 +0900
@@ -26,10 +26,10 @@
#include <linux/platform_data/irq-renesas-irqc.h>
#include <linux/serial_sci.h>
#include <linux/sh_timer.h>
-#include <mach/common.h>
-#include <mach/irqs.h>
-#include <mach/r8a7791.h>
-#include <mach/rcar-gen2.h>
+#include "common.h"
+#include "irqs.h"
+#include "r8a7791.h"
+#include "rcar-gen2.h"
#include <asm/mach/arch.h>
static const struct resource pfc_resources[] __initconst = {
--- 0001/arch/arm/mach-shmobile/smp-r8a7791.c
+++ work/arch/arm/mach-shmobile/smp-r8a7791.c 2014-02-24 13:48:39.000000000 +0900
@@ -18,8 +18,8 @@
#include <linux/smp.h>
#include <linux/io.h>
#include <asm/smp_plat.h>
-#include <mach/common.h>
-#include <mach/r8a7791.h>
+#include "common.h"
+#include "r8a7791.h"
#define RST 0xe6160000
#define CA15BAR 0x0020
next prev parent reply other threads:[~2014-02-24 5:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 5:40 [PATCH 00/12] ARM: shmobile: Rework include path for SoC files Magnus Damm
2014-02-24 5:41 ` [PATCH 01/12] ARM: shmobile: Add temporary include workaround Magnus Damm
2014-02-24 6:25 ` Magnus Damm
2014-02-24 5:41 ` [PATCH 02/12] ARM: shmobile: Rework include path for sh7372 Magnus Damm
2014-02-24 5:41 ` [PATCH 03/12] ARM: shmobile: Rework include path for sh73a0 Magnus Damm
2014-02-24 5:41 ` [PATCH 04/12] ARM: shmobile: Rework include path for EMEV2 Magnus Damm
2014-02-24 5:41 ` [PATCH 05/12] ARM: shmobile: Rework include path for r8a7740 Magnus Damm
2014-02-24 5:41 ` [PATCH 06/12] ARM: shmobile: Rework include path for r8a7778 Magnus Damm
2014-02-24 5:42 ` [PATCH 07/12] ARM: shmobile: Rework include path for r8a7779 Magnus Damm
2014-02-24 5:42 ` [PATCH 08/12] ARM: shmobile: Rework include path for r8a7790 Magnus Damm
2014-02-24 5:42 ` Magnus Damm [this message]
2014-02-24 5:42 ` [PATCH 10/12] ARM: shmobile: Rework include path for r8a73a4 Magnus Damm
2014-02-24 5:42 ` [PATCH 11/12] ARM: shmobile: Rework include path for r7s72100 Magnus Damm
2014-02-24 5:42 ` [PATCH 12/12] ARM: shmobile: Rework include path for common bits Magnus Damm
2014-03-07 2:38 ` [PATCH 00/12] ARM: shmobile: Rework include path for SoC files Simon Horman
2014-03-10 8:47 ` Simon Horman
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=20140224054223.1143.82115.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--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).