From mboxrd@z Thu Jan 1 00:00:00 1970 From: paul@pwsan.com (Paul Walmsley) Date: Tue, 26 Jun 2012 04:39:19 -0600 (MDT) Subject: [PATCH 08/11] crypto: omap: add clk_prepare and clk_unprepare In-Reply-To: <4FE7F73D.6090402@ti.com> References: <1340372890-10091-1-git-send-email-rnayak@ti.com> <1340372890-10091-9-git-send-email-rnayak@ti.com> <4FE7F73D.6090402@ti.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, 25 Jun 2012, Rajendra Nayak wrote: > So if CCF conversion patches get in before these get converted to > runtime PM, do we break them? or should CCF conversion for OMAP > wait till all remaining drivers get converted to runtime PM? I'd suggest getting patches 1, 10, and 11 from your series in shape and PM-tested. Those shouldn't have any driver dependencies, so once those are in good condition, they can be merged through the OMAP tree. Then at the same time, maybe get the rest of the drivers runtime-PM converted and acked through their respective maintainers. Looks like you have a couple of driver patches that don't involve runtime-PM conversions; those can presumably get merged through their respective maintainers? ... I did notice that some other driver conversions weren't present in this series, e.g., omap3isp. If someone doesn't convert those drivers, then those seem likely to break. - Paul