On Sun, 8 Oct 2017 12:09:50 +0200 Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx> wrote: > On Sun, 08 Oct 2017 11:53:11 +0200 > Robert Jarzmik <robert.jarzmik@xxxxxxx> wrote: > > > Robert Jarzmik <robert.jarzmik@xxxxxxx> writes: > > > > > Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx> writes: > > > > > >> Hi Robert, > > >> Wait a bit before applying. I think patches 6 to 9 have a dependency on > > >> patch 1 (it's not a build dependency, but NAND partitioning might be > > >> wrong if you apply them), so we need to sync. What release is > > >> pxa/for-next targeting? If it's 4.15 I can apply patch 1 just after > > >> 4.14-rc1 is out and provide an immutable branch for you to pull in > > >> pxa/for-next. > > > > > > Hi Boris, > > > > > > It's targeting 4.15 right now. And we can do as you like, either an immutable > > > branch, or I wait to include these patches into my pxa/for-next until you give > > > me your go, it's as you like. > > > > Hi Boris, > > > > So what's the status about the sync, should I pick the patches, and have the > > others make it to your for-next branch ? > > I'm still waiting Brian's final word about this version, and if he's > happy with it, Richard will queue it for 4.15. Actually, I'm waiting a feedback on v9 [1], not v5. [1]http://patchwork.ozlabs.org/patch/808431/ -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
