From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: "Russell King" <linux@arm.linux.org.uk>,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Javier Martinez Canillas" <javier.martinez@collabora.co.uk>
Subject: [RESEND PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC driver
Date: Wed, 19 Mar 2014 07:08:14 +0100 [thread overview]
Message-ID: <1395209295-24399-3-git-send-email-javier.martinez@collabora.co.uk> (raw)
In-Reply-To: <1395209295-24399-1-git-send-email-javier.martinez@collabora.co.uk>
The GPMC driver includes arch/arm/mach-omap2/common.h but
does not use anything on that header so it can be removed.
Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
arch/arm/mach-omap2/gpmc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index ab43755..b637c96 100644
--- a/arch/arm/mach-omap2/gpmc.c
+++ b/arch/arm/mach-omap2/gpmc.c
@@ -37,7 +37,6 @@
#include <asm/mach-types.h>
#include "soc.h"
-#include "common.h"
#include "omap_device.h"
#include "gpmc.h"
#include "gpmc-nand.h"
--
1.9.0
next prev parent reply other threads:[~2014-03-19 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 6:08 [RESEND PATCH 0/3] ARM: OMAP2+: Remove remaining unused legacy code Javier Martinez Canillas
2014-03-19 6:08 ` [RESEND PATCH 1/3] ARM: OMAP2+: Remove legacy smsc911x and smc91x GPMC support Javier Martinez Canillas
2014-03-19 6:08 ` Javier Martinez Canillas [this message]
2014-11-06 18:52 ` [RESEND PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC driver Tony Lindgren
2014-11-06 20:17 ` Javier Martinez Canillas
2014-03-19 6:08 ` [RESEND PATCH 3/3] ARM: OMAP2+: Remove legacy board-flash.c Javier Martinez Canillas
2014-03-19 16:05 ` [RESEND PATCH 0/3] ARM: OMAP2+: Remove remaining unused legacy code Tony Lindgren
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=1395209295-24399-3-git-send-email-javier.martinez@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
/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).