* Santosh Shilimkar <santosh.shilimkar@xxxxxx> [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@xxxxxx> [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@xxxxxx> > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
