linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: linux-omap@vger.kernel.org,
	Omar Ramirez Luna <omar.luna@linaro.org>,
	Paul Walmsley <paul@pwsan.com>,
	Igor Grinberg <grinberg@compulab.co.il>,
	Felipe Balbi <balbi@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Keshava Munegowda <keshava_mgowda@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: Re: Updated status of the removal of plat headers
Date: Wed, 17 Oct 2012 15:02:03 -0700	[thread overview]
Message-ID: <20121017220203.GZ15569@atomide.com> (raw)
In-Reply-To: <507F2875.2050406@ti.com>

* Jon Hunter <jon-hunter@ti.com> [121017 14:53]:
> Hi Tony,
> 
> On 10/16/2012 06:00 PM, Tony Lindgren wrote:
> > Hi all,
> > 
> > Here's a quick status update on the removal of remaining
> > #include <plat/*.h> files. Most files are now fixed up, and
> > we only have the following remaining:
> > 
> > cpu.h		wrapper only left, will be removed as soon as drivers are fixed
> > 
> > dmtimer.h	Jon is fixing this
> 
> I have patches ready for this. However, as you know I have a few timer
> series cooking at the moment and just sent out the latest timer DT
> series today [1][2].
> 
> I have also updated my timer fixes series [3] too, however, I was not
> going to send out until the DT stuff is sorted. At the moment I have
> included the dmtimer header patches with the fixes series as there are
> some dependencies but this series has now grown into a 20+ patch series.
> So if it is easier to manage, I could split this into a fixes series and
> a clean-up series. Or if you only want the header stuff now, I could
> send this and send the fixes and clean-up later.

When they are ready, two separate pull requests against v3.7-rc1 for fixes
and cleanup would be perfect.

Thanks,

Tony
 
> [1] http://marc.info/?l=linux-omap&m=135049690119218&w=2
> [2] http://marc.info/?l=linux-omap&m=135049882020029&w=2
> [3] http://marc.info/?l=linux-arm-kernel&m=134687192121865&w=2

  reply	other threads:[~2012-10-17 22:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 23:00 Updated status of the removal of plat headers Tony Lindgren
2012-10-17  0:24 ` Paul Walmsley
2012-10-17 15:43 ` [PATCH] arm: omap: move OMAP USB platform data to <linux/platform_data/omap-usb.h> Felipe Balbi
2012-10-17 15:45   ` Felipe Balbi
2012-10-17 15:47 ` [PATCH v2] " Felipe Balbi
2012-10-17 20:34   ` Tony Lindgren
2012-10-18  5:49     ` Felipe Balbi
2012-10-19  1:49       ` Tony Lindgren
2012-10-19  6:55         ` Felipe Balbi
2012-10-19 15:56           ` Tony Lindgren
2012-10-17 21:51 ` Updated status of the removal of plat headers Jon Hunter
2012-10-17 22:02   ` Tony Lindgren [this message]
2012-10-19 17:43 ` Omar Ramirez Luna
2012-10-19 18:25   ` 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=20121017220203.GZ15569@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=grinberg@compulab.co.il \
    --cc=jon-hunter@ti.com \
    --cc=keshava_mgowda@ti.com \
    --cc=kishon@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=omar.luna@linaro.org \
    --cc=paul@pwsan.com \
    --cc=tomi.valkeinen@ti.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).