On 04/19/2013 03:36 PM, Arnd Bergmann wrote: > On Thursday 11 April 2013, Arnd Bergmann wrote: >> These are the patches that I would like to apply directly to >> the arm-soc next/multiplatform branch, unless you have any >> objections. This would get all the simple stuff out of the >> way, and I don't think there is a big risk of introducing >> regressions with these. >> >> A lot of the other patches have already been merged into >> subsystem trees. After this series in in arm-soc, what is >> left comes down to >> >> * The ASoC conversion to dmaengine won't make it unless someone >> who knows that code better steps up to do it right away. This >> means that we won't have audio in a 3.10 multiplatform kernel >> on Exynos, but it will still work for users that don't enable >> multiplatform. >> >> * The irqchip (combiner), clk and clksource patches are all based >> on top of other changesets we pulled in from your trees, so I >> would not make them part of the next/multiplatform branch. We can >> apply them on top of the next/drivers branch once they are >> tested successfully. >> >> * A trivial patch is needed in the end to actually make >> CONFIG_ARCH_EXYNOS visible in multiplatform configurations. >> We will do that as a separate patch once everything else is >> there. >> >> Please provide an ACK so I can put this into arm-soc, or let >> me know if I screwed up somewhere. > > No reply? > > I'm putting them into the next/multiplatform branch now, with > the exception of the i2c patch that is already in the i2c > tree. > > I've tested this on the Arndale board and am putting it into > the next/multiplatform branch now as a stepping stone for > part two, which will be a late branch at best, if we decide > to merge it in 3.10. I've reviewed this patch series and nothing concerning jumps. Please feel free to add Reviewed-by: Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> if still possible. Thanks. Sylwester -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |