On Tue, Feb 11, 2014 at 03:49:24PM +0000, Gupta, Pekon wrote: > Hi Ezequiel, > > >From: Ezequiel Garcia [mailto:[email protected]] > >> diff --git a/Documentation/devicetree/bindings/mtd/nand.txt > >> b/Documentation/devicetree/bindings/mtd/nand.txt > >> index 03855c8..683a310 100644 > >> --- a/Documentation/devicetree/bindings/mtd/nand.txt > >> +++ b/Documentation/devicetree/bindings/mtd/nand.txt > >> @@ -3,5 +3,9 @@ > >> - nand-ecc-mode : String, operation mode of the NAND ecc mode. > >> Supported values are: "none", "soft", "hw", "hw_syndrome", > >> "hw_oob_first", > >> "soft_bch". > >> > Should nand-ecc-mode also be marked as <deprecated>, and but we continue > supporting it in kernel code ?
No, I wouldn't deprecate them, as they're in use by the atmel-nand and mxc-nand drivers. > If yes, then what is the life-time of these <deprecated> bindings. > I mean exactly how many kernel versions should > continue support deprecated bindings ? > Well, if we ever decide to deprecate a DT binding, I'd say we must keep backwards compatible forever. Yes, forever. Or at least, until the last user dies or we can steal his board :-) -- Ezequiel García, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
