linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP2+: Remove remaining unused legacy code
Date: Wed, 4 Dec 2013 09:53:10 -0800	[thread overview]
Message-ID: <20131204175310.GR26766@atomide.com> (raw)
In-Reply-To: <1385752697-13700-1-git-send-email-javier.martinez@collabora.co.uk>

* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131129 11:20]:
> Now that OMAP2+ board files are scheduled for removal for v3.14
> 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
> 
> and is composed of the following patches:
> 
> [PATCH 1/3] ARM: OMAP2+: Remove legacy smsc911x and smc91x GPMC
> [PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC driver
> [PATCH 3/3] ARM: OMAP2+: Remove legacy board-flash.c

Thanks looks good to me. I'll wait for -rc3 to get tagged and then
apply all the pending mach-omap2 device tree conversion patches
against it including these.

Regards,

Tony

      parent reply	other threads:[~2013-12-04 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 19:18 [PATCH 0/3] ARM: OMAP2+: Remove remaining unused legacy code Javier Martinez Canillas
2013-11-29 19:18 ` [PATCH 1/3] ARM: OMAP2+: Remove legacy smsc911x and smc91x GPMC support Javier Martinez Canillas
2013-11-29 19:18 ` [PATCH 2/3] ARM: OMAP2+: Remove unnecesary include in GPMC driver Javier Martinez Canillas
2013-11-29 19:18 ` [PATCH 3/3] ARM: OMAP2+: Remove legacy board-flash.c Javier Martinez Canillas
2013-12-04 17:53 ` Tony Lindgren [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=20131204175310.GR26766@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).