>>-----Original Message----- >>From: Paul Walmsley [mailto:paul@xxxxxxxxx] >>Sent: Thursday, January 21, 2010 11:54 AM >>To: Gopinath, Thara >>Cc: linux-omap@xxxxxxxxxxxxxxx; khilman@xxxxxxxxxxxxxxxxxxx >>Subject: Re: [PATCH 0/8] OMAP3: PM: Open Switch Retention support in the cpuidle thread. >> >> >>Hi Thara, >> >>I'd like to merge the powerdomain changes separately from the other >>changes, most of which should probably go through Kevin's PM branch. >> >>After you revise your patches based on the comments, can you take your >>patches 3, 4, and the powerdomain portions of patch 7 and post those in a >>separate series as an OSWR preparatory powerdomain patch set? That will >>make it easier for both Kevin and I to handle. When you say patch 7, I believe you are mentioning the book keeping part for OSWR where logic_ret_off and mem_ret_off counters are added. I can separate this out and post these three patches separately. Do let me know should I base these on linux-omap master branch or Kevin's pm tree. >> >>Note: the powerdomain code will need to be edited somewhat to bring it >>up-to-date with the latest OMAP4 changes in the for_2.6.34 branch, which >>is where your patches will go. I'm happy to do this, but after I do it, >>will you be able to test the updated series to ensure that this process >>didn't break anything? Thanks for this and sure I can test the updated series! But I do not understand what OMAP4 specific support has to be added for these three patches. These three patches will be considerably free of OMAP2/OMAP3/OMAP4 specific stuff. Or are you talking of rebasing on 2.6.34 kernel? Regards Thara -- 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
