From: Artem Bityutskiy Date: Fri, 3 Feb 2012 07:44:32 +0000 (+0200) Subject: mtd: docg3: initialize writebufsize X-Git-Tag: upstream/snapshot3+hdmi~7793^2~87 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=82c4c58d6f1a78e8de875272a19ab9220b8066aa;p=platform%2Fadaptation%2Frenesas_rcar%2Frenesas_kernel.git mtd: docg3: initialize writebufsize The writebufsize concept was introduce by commit "0e4ca7e mtd: add writebufsize field to mtd_info struct" and it represents the maximum amount of data the device writes to the media at a time. This is an important parameter for UBIFS which is used during recovery and which basically defines how big a corruption caused by a power cut can be. Set it to be equivalent to mtd->writesize because this is the maximum amount of data the driver writes at a time. Signed-off-by: Artem Bityutskiy Acked-by: Robert Jarzmik Cc: stable@kernel.org [3.2+] Signed-off-by: David Woodhouse --- diff --git a/drivers/mtd/devices/docg3.c b/drivers/mtd/devices/docg3.c index 3746ae8..fc7932b 100644 --- a/drivers/mtd/devices/docg3.c +++ b/drivers/mtd/devices/docg3.c @@ -1817,7 +1817,7 @@ static void __init doc_set_driver_info(int chip_id, struct mtd_info *mtd) mtd->erasesize = DOC_LAYOUT_BLOCK_SIZE * DOC_LAYOUT_NBPLANES; if (docg3->reliable == 2) mtd->erasesize /= 2; - mtd->writesize = DOC_LAYOUT_PAGE_SIZE; + mtd->writebufsize = mtd->writesize = DOC_LAYOUT_PAGE_SIZE; mtd->oobsize = DOC_LAYOUT_OOB_SIZE; mtd->owner = THIS_MODULE; mtd->_erase = doc_erase;