On Wed, Jul 16, 2014 at 02:59:05PM +0200, Thomas Petazzoni wrote:

Dear Jason Cooper,

On Wed, 16 Jul 2014 08:45:22 -0400, Jason Cooper wrote:

quoted

Ok, so I applied patch #10 to mvebu/dt, and #17 to mvebu/defconfig.  I
was then going to apply the rest into a tentative topic branch
(mvebu/soc-cpuidle), but it failed when based on v3.16-rc1, and it
failed when based on mvebu/soc.

Could you please outline the deps so I can get this into -next?  We're
really cutting the deadline close for v3.17, and I'd like to already
have some time in -next if/when cpuidle Ack's it going through the mvebu
tree.

As explained in the cover letter:

Gah!  I missed that it was listed in the changes.  Thanks!

 * Series rebased on top of mvebu/fixes + mvebu/soc to take into
   account the conflicts with the changes already merged on the PMSU
   code.

Yup, I missed the dep on mvebu/fixes.

thx,

Jason.