From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC driver
Date: Thu, 6 Nov 2014 10:52:36 -0800 [thread overview]
Message-ID: <20141106185235.GD31454@atomide.com> (raw)
In-Reply-To: <1395209295-24399-3-git-send-email-javier.martinez@collabora.co.uk>
* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [140318 23:12]:
> 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>
Probably meant Cc here? :) I'll apply this into omap-for-v3.19/gpmc,
the rest will need to wait until omap3 is DT only.
Regards,
Tony
> ---
> 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-11-06 18:52 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 ` [RESEND PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC driver Javier Martinez Canillas
2014-11-06 18:52 ` Tony Lindgren [this message]
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=20141106185235.GD31454@atomide.com \
--to=tony@atomide.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).