From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
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
Subject: Re: [RESEND PATCH 0/3] ARM: OMAP2+: Remove remaining unused legacy code
Date: Wed, 19 Mar 2014 09:05:13 -0700 [thread overview]
Message-ID: <20140319160513.GC12934@atomide.com> (raw)
In-Reply-To: <1395209295-24399-1-git-send-email-javier.martinez@collabora.co.uk>
* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [140318 23:12]:
> Once OMAP2+ board files are removed, there is unused code that was only used
> by legacy platform code and can be removed.
>
> This patch-set depends on the series:
>
> [PATCH 00/12] Drop omap3 board files and make mach-omap2 boot in DT only mode [0]
>
> and is composed of the following patches:
>
> [RESEND PATCH 1/3] ARM: OMAP2+: Remove legacy smsc911x and smc91x
> [RESEND PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC
> [RESEND PATCH 3/3] ARM: OMAP2+: Remove legacy board-flash.c
>
> Tony,
>
> I don't know what is your new schedule for board files removal but in case it is
> 3.16, I forward ported this patch-set on top of 3.14-rc7 and fixed some conflicts.
Thanks, I'll also rebase my changes in omap-for-v3.14/omap3-board-removal
at some point. Probably a good target is v3.16 if the DSS changes go
in. Then we just need displays enabled for omap3 and pandora supported
to drop the legacy data AFAIK.
Regards,
Tony
> [0]: http://marc.info/?t=138542504600001&r=1&w=2
>
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 0/3] ARM: OMAP2+: Remove remaining unused legacy code
Date: Wed, 19 Mar 2014 09:05:13 -0700 [thread overview]
Message-ID: <20140319160513.GC12934@atomide.com> (raw)
In-Reply-To: <1395209295-24399-1-git-send-email-javier.martinez@collabora.co.uk>
* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [140318 23:12]:
> Once OMAP2+ board files are removed, there is unused code that was only used
> by legacy platform code and can be removed.
>
> This patch-set depends on the series:
>
> [PATCH 00/12] Drop omap3 board files and make mach-omap2 boot in DT only mode [0]
>
> and is composed of the following patches:
>
> [RESEND PATCH 1/3] ARM: OMAP2+: Remove legacy smsc911x and smc91x
> [RESEND PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC
> [RESEND PATCH 3/3] ARM: OMAP2+: Remove legacy board-flash.c
>
> Tony,
>
> I don't know what is your new schedule for board files removal but in case it is
> 3.16, I forward ported this patch-set on top of 3.14-rc7 and fixed some conflicts.
Thanks, I'll also rebase my changes in omap-for-v3.14/omap3-board-removal
at some point. Probably a good target is v3.16 if the DSS changes go
in. Then we just need displays enabled for omap3 and pandora supported
to drop the legacy data AFAIK.
Regards,
Tony
> [0]: http://marc.info/?t=138542504600001&r=1&w=2
>
next prev parent reply other threads:[~2014-03-19 16:05 UTC|newest]
Thread overview: 14+ 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 ` 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
2014-03-19 6:08 ` [RESEND PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC driver Javier Martinez Canillas
2014-03-19 6:08 ` Javier Martinez Canillas
2014-11-06 18:52 ` Tony Lindgren
2014-11-06 18:52 ` Tony Lindgren
2014-11-06 20:17 ` Javier Martinez Canillas
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 6:08 ` Javier Martinez Canillas
2014-03-19 16:05 ` Tony Lindgren [this message]
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=20140319160513.GC12934@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.