Hi Pekon, I don't think I will take this series (at least not yet), because of the device-tree ABI breakage. On Sun, Jul 14, 2013 at 02:24:47AM +0530, Pekon Gupta wrote: > > Changes v4 -> v5 > - Rebased to linux-next > IMPORTANT: Need to revert commit fb1585b, [PATCH 2/4] part of previous version > http://lists.infradead.org/pipermail/linux-mtd/2013-July/047441.html > > - Swapped PATCH-1 & PATCH-2 to maintain bisectibility & compilation dependency > http://lists.infradead.org/pipermail/linux-mtd/2013-July/047461.html > > - PATCH-2: re-ordered call to is_elm_present() for later updates ELM driver > - dropped changes in include/linux/platform_data/elm.h (not needed) > - PATCH-3: re-ordered call to is_elm_present() for later updates ELM driver > - Re-formated patch description (replaced tabs with white-spaces) > > > Changes v3 -> v4 > (Resent with CC: devicetree-discuss@xxxxxxxxxxxxxxxx) Make sure to use devicetree@xxxxxxxxxxxxxxx for future series. > - [Patch 1/3] removed MTD_NAND_OMAP_BCH8 & MTD_NAND_OMAP_BCH4 from nand/Kconfig > ECC scheme selectable via nand DT (nand-ecc-opt). > - [*] rebased for l2-mtd.git > > > Changes v2 -> v3 > (Resent with Author Name fixed) > - PATCH-1: re-arranged code to remove redundancy, added NAND_BUSWIDTH_AUTO > - PATCH-2: updated nand-ecc-opt DT mapping and Documentation > - PATCH-3: code-cleaning + changes to match PATCH-1 > - PATCH-4 <DROPPED> update DT attribute for ti,nand-ecc-opt > - received feedback to keep DT mapping independent of linuxism > - PATCH-4:<NEW> : ARM: dts: AM33xx: updated default ECC scheme in nand-ecc-opt > - independent patch for AM335x-evm.dts update based on PATCH-2 > > > Changes v1 -> v2 > added [PATCH 3/4] and [PATCH 4/4] [...] You might also consider a future patch for utilizing devm_* functions for the probe/remove routines in drivers/mtd/nand/omap2.c. That could improve some of the stuff I looked at in this series. Brian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html