On Fri, 2014-10-24 at 08:30 -0600, Lina Iyer wrote: > On Fri, Oct 24 2014 at 04:01 -0600, Ivan T. Ivanov wrote: > > > > > >On Thu, 2014-10-23 at 09:54 -0600, Lina Iyer wrote: > > > On Thu, Oct 23 2014 at 09:31 -0600, Ivan T. Ivanov wrote: > > > > > > > > > > > >Hi, > > > > > > > > > > > >On Tue, 2014-10-07 at 15:41 -0600, Lina Iyer wrote: > > > > > Hi, > > > > > > > > > > > > This v8 revision of the cpuidle driver is available at > > > > > git.linaro.org:/people/lina.iyer/linux-next cpuidle-v8 > > > > > > > > > > > > > > > > > > >Probably I missing something, but should I expect that > > > > > >once these patches are applied driver could be successfully > > > > compiled? > > > Yes they should. > > > > > >Do these patches depends on other patches, which I am missing. > > >I am applying them on current linus/master. At least > > > > >and <soc/qcom/scm-boot.h> are missing from this patch-set v8 :-| > > > > > Oh sorry, if you look at the cover letter, in the past, these patches > have been pulled in or being staged. > > You can get the tree and the the patches from > https://git.linaro.org/people/lina.iyer/linux-next.git/shortlog/refs/heads/cpuidle-v8 > > which are on top of 3.17-rc1, but you should be able to pull it on > top > of yours, without any issue. Do note that some of these patches that > I > have on top of 3.17-rc1 (like the ARM idle states) may already be > available in linus/master. > > Hope that helps. Yep, this is better. Thank you, Ivan -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html