From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Kristo, Tero" <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>,
Rajendra Nayak <rnayak@ti.com>,
"Valentin, Eduardo" <eduardo.valentin@ti.com>,
"Anna, Suman" <s-anna@ti.com>,
"Bedia, Vaibhav" <vaibhav.bedia@ti.com>,
Vaibhav Hiremath <hvaibhav@ti.com>
Subject: Re: [GIT PULL] ARM: OMAP5: hwmod, prm/cm data files and updates for 3.10
Date: Fri, 17 May 2013 10:22:31 -0700 [thread overview]
Message-ID: <20130517172231.GW5600@atomide.com> (raw)
In-Reply-To: <5195E380.4040103@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [130517 01:02]:
> Paul, Tony,
>
> On Friday 05 April 2013 10:20 PM, Santosh Shilimkar wrote:
> > On Thursday 04 April 2013 10:27 PM, Santosh Shilimkar wrote:
> >> On Thursday 04 April 2013 10:22 PM, Tony Lindgren wrote:
> >>> * Santosh Shilimkar <santosh.shilimkar@ti.com> [130404 04:15]:
> > [..]
> >
> >>> Can't we already trim the am33xx hwmod data after your patches for
> >>> v3.10 as am33xx is already DT only? Unfortunately we cannot create
> >>> negative diffstat in other ways for v3.10 merge window as we cannot
> >>> make omap4 DT only just quite yet.
> >>>
> >> Yes we can and I can take a stab it tomorrow. The only thing is I
> >> might need some support for testing but thats manageable. Will
> >> take a stab at it tomorrow and if everything goes well, post a
> >> patch for smae.
> >>
> > Patch for the AM33XX to trim is end of the email. Thanks to
> > Sricharan and Pekon for patch and testing. Looping both
> > Vaibhav's if they have any objection on the patch.
> >
> > Regards,
> > Santosh
> >
> > From b95dd33fe59b8e77727eb3b1717d763bbf9a2893 Mon Sep 17 00:00:00 2001
> > From: Sricharan R <r.sricharan@ti.com>
> > Date: Fri, 5 Apr 2013 20:39:12 +0530
> > Subject: [PATCH] ARM: AM33XX: hwmod data: Clean up the data file
> >
> For whatever reason, we again missed the merge window for the subject
> series, I would like to know your plan on the subject series for
> at least 3.11. Asking *well in advance* to avoid late merge related
> discussions.
Yes, I think we should have now a omap5 hwmod data sized hole coming
up with conversion of omap4 to be DT only. I'll post those patches
today for the board file and legacy mux removal for omap4:
12 files changed, 52 insertions(+), 3260 deletions(-)
Those coupled with your am33xx hwmod cleanup patch and your omap4
hwmod cleanup patch should allow us having the omap5 hwmod data
without making the diffstats look too bad.
> Thanks to Vaibhav, AM33XX patch is tested and validated with some
> updates considering upcoming PM support for AM33XX. So that
> patch will be included in the series.
>
> Rajendra will follow up the patchset if there is some re-basing is
> needed since I will away for few weeks because of travel.
OK, well the omap4 hwmod clean-up patch depends on first dropping
the above mentioned omap4 legacy files.
> OMAP5 data is the *only* thing which is gating the device to boot
> from mainline.
That's great!
Regards,
Tony
next prev parent reply other threads:[~2013-05-17 17:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 8:40 [GIT PULL] ARM: OMAP5: hwmod, prm/cm data files and updates for 3.10 Santosh Shilimkar
2013-04-01 17:05 ` Tony Lindgren
2013-04-03 3:52 ` Santosh Shilimkar
2013-04-03 19:42 ` Paul Walmsley
2013-04-04 11:12 ` Santosh Shilimkar
2013-04-04 16:52 ` Tony Lindgren
2013-04-04 16:57 ` Santosh Shilimkar
2013-04-05 16:50 ` Santosh Shilimkar
2013-04-05 17:10 ` Tony Lindgren
2013-04-09 18:03 ` Hiremath, Vaibhav
2013-04-10 11:15 ` Hiremath, Vaibhav
2013-04-10 11:32 ` Santosh Shilimkar
2013-04-15 5:06 ` Hiremath, Vaibhav
2013-04-15 6:20 ` Santosh Shilimkar
2013-04-18 4:49 ` Hiremath, Vaibhav
2013-04-10 11:23 ` Hiremath, Vaibhav
2013-05-17 8:00 ` Santosh Shilimkar
2013-05-17 17:22 ` Tony Lindgren [this message]
2013-05-29 16:41 ` Santosh Shilimkar
2013-04-05 12:42 ` Tero Kristo
2013-04-03 20:09 ` Paul Walmsley
2013-04-04 10:34 ` Santosh Shilimkar
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=20130517172231.GW5600@atomide.com \
--to=tony@atomide.com \
--cc=eduardo.valentin@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=s-anna@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.com \
--cc=vaibhav.bedia@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