diff options
| author | Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | 2012-02-03 08:53:28 +0100 |
|---|---|---|
| committer | David Woodhouse <David.Woodhouse@intel.com> | 2012-03-27 01:23:01 +0200 |
| commit | fcc44a07dae0af16e84e93425fc8afe642ddc603 (patch) | |
| tree | b68fd1dd9a87c8996d511f62b89faf95f7e2414b /usr | |
| parent | mtd: docg3: initialize writebufsize (diff) | |
| download | linux-fcc44a07dae0af16e84e93425fc8afe642ddc603.tar.xz linux-fcc44a07dae0af16e84e93425fc8afe642ddc603.zip | |
mtd: lart: 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 writebufsize to 4 because this drivers writes at max 4 bytes 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>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions