Hi Ivan, On Sat, May 19, 2012 at 18:20:18, Ivan Djelic wrote: > Hi Afzal, > > I tried to take your series of patches, but I had issues with the > first [1] (I did not try the others): it depends on the following patch, > which is not in the l2-mtd-2.6 tree: > > http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg68258.html > > and it does not apply anyway to l2-mtd-2.6 because of (at least) the > following patches: > > http://lists.infradead.org/pipermail/linux-mtd/2012-April/040631.html > http://lists.infradead.org/pipermail/linux-mtd/2012-April/040724.html > > So, do you think you could rebase your series on l2-mtd-2.6 ? > And maybe merge the 3 series into a single one, if they have circular > dependencies ? I am not sure what the workflow should be here, all patch series were made over omap tree, if it is generated over mtd tree, similar issue would happen for omap platform patches. In any case, for your reference, the 3 series of patches of had been rebased over mtd tree, and is available, git@xxxxxxxxxxxxx:x0148406-public/linux-kernel.git gpmc-mtd. To prevent confusion the 3 patch series has not been posted. Tony, Artem, how should the conflict between omap & mtd trees be handled for patch series ? I believe it is better to send the 3 patch series into one as mentioned by Ivan, and planning to do so, but in that case over which tree should it be based ? Regards Afzal -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
