| commit | cca84b569ebe3372b28949e00b0a3a17f87e2970 | |
| author | Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | |
| Fri, 3 Feb 2012 07:42:39 +0000 (3 09:42 +0200) | ||
| committer | David Woodhouse <David.Woodhouse@intel.com> | |
| Mon, 26 Mar 2012 23:22:46 +0000 (27 00:22 +0100) | ||
| tree | 6625a62001e9a58f6cebd7121423e245ed8bc7bd | treesnapshot (tar.gz zip) |
| parent | cd1986a3c111f7ed597619705290fa52a975014f | commitdiff |
mtd: doc2001: 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 <artem.bityutskiy@linux.intel.com>
Cc: stable@kernel.org [2.6.38+]
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
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 <artem.bityutskiy@linux.intel.com>
Cc: stable@kernel.org [2.6.38+]
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
| drivers/mtd/devices/doc2001.c | diffblobblamehistory |