On Thu, May 10, 2012 at 02:07:37PM +0100, Artem Bityutskiy wrote: > On Wed, 2012-05-09 at 08:31 -0700, Tony Lindgren wrote: > > > Note that I could prepare a new MTD patch with BCH ecc code included, > > > allowing to drop the GPMC BCH ecc api. > > > > OK, let's do that then. I'll drop this patch and you can coordinate > > your patch with Afzal. > > Ivan, so are you going to send new patches early enough to make them hit > 3.5? Can you please then re-send all the dependent patches again and > again describe what depends on what, because I am getting lost :-) Yes, I agree this has become a bit confusing. I currently have 2 pending patches: [1] ARM-OMAP3-gpmc-add-BCH-ecc-api-and-modes_v3.patch (linux-omap) [2] mtd-nand-omap-add-support-for-hardware-BCH-ecc_v2.patch (linux-mtd) They should both be dropped. I will basically merge the two patches and submit a new single patch on MTD only, with no dependency. I won't need to patch arch/arm/mach-omap2 anymore. But in order to do so, I need the changes that Afzal has submitted (in particular [3]). Those changes (and as a consequence, my new patch) won't hit 3.5. So, when Afzal's patches are pushed, I'll submit a new, single MTD patch. BR, -- Ivan [1] http://lists.infradead.org/pipermail/linux-mtd/2012-April/040965.html [2] http://lists.infradead.org/pipermail/linux-mtd/2012-April/041020.html [3] http://lists.infradead.org/pipermail/linux-mtd/2012-May/041105.html -- 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
