X-Git-Url: http://git.monstr.eu/?a=blobdiff_plain;ds=sidebyside;f=Documentation%2Fdevicetree%2Fbindings%2Fmtd%2Fgpmc-nand.txt;h=c459f169a9044a91c919e8eb96c0776aa9acbd88;hb=6b6dc4f40c5264556223ba94693f20d83796ab1f;hp=44919d48d2415c4fadc80dd5ed02e291b7dcc640;hpb=c212ddaee2fd21e8d756dbc3c6119e3259b38fd0;p=linux-2.6-microblaze.git

diff --git a/Documentation/devicetree/bindings/mtd/gpmc-nand.txt b/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
index 44919d48d241..c459f169a904 100644
--- a/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
+++ b/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
@@ -122,7 +122,7 @@ on various other factors also like;
 	so the device should have enough free bytes available its OOB/Spare
 	area to accommodate ECC for entire page. In general following expression
 	helps in determining if given device can accommodate ECC syndrome:
-	"2 + (PAGESIZE / 512) * ECC_BYTES" >= OOBSIZE"
+	"2 + (PAGESIZE / 512) * ECC_BYTES" <= OOBSIZE"
 	where
 		OOBSIZE		number of bytes in OOB/spare area
 		PAGESIZE	number of bytes in main-area of device page