mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-25 18:30:06 +00:00
UBI: Fix typos
Signed-off-by: Andrew F. Davis <afd@ti.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
parent
12f54139d8
commit
2fae13124f
3 changed files with 3 additions and 4 deletions
|
@ -2,7 +2,7 @@ menuconfig MTD_UBI
|
|||
tristate "Enable UBI - Unsorted block images"
|
||||
select CRC32
|
||||
help
|
||||
UBI is a software layer above MTD layer which admits of LVM-like
|
||||
UBI is a software layer above MTD layer which admits use of LVM-like
|
||||
logical volumes on top of MTD devices, hides some complexities of
|
||||
flash chips like wear and bad blocks and provides some other useful
|
||||
capabilities. Please, consult the MTD web site for more details
|
||||
|
|
|
@ -45,7 +45,7 @@
|
|||
* About minimal I/O units. In general, UBI assumes flash device model where
|
||||
* there is only one minimal I/O unit size. E.g., in case of NOR flash it is 1,
|
||||
* in case of NAND flash it is a NAND page, etc. This is reported by MTD in the
|
||||
* @ubi->mtd->writesize field. But as an exception, UBI admits of using another
|
||||
* @ubi->mtd->writesize field. But as an exception, UBI admits use of another
|
||||
* (smaller) minimal I/O unit size for EC and VID headers to make it possible
|
||||
* to do different optimizations.
|
||||
*
|
||||
|
|
|
@ -544,8 +544,7 @@ struct ubi_debug_info {
|
|||
* @vid_hdr_aloffset: starting offset of the VID header aligned to
|
||||
* @hdrs_min_io_size
|
||||
* @vid_hdr_shift: contains @vid_hdr_offset - @vid_hdr_aloffset
|
||||
* @bad_allowed: whether the MTD device admits of bad physical eraseblocks or
|
||||
* not
|
||||
* @bad_allowed: whether the MTD device admits bad physical eraseblocks or not
|
||||
* @nor_flash: non-zero if working on top of NOR flash
|
||||
* @max_write_size: maximum amount of bytes the underlying flash can write at a
|
||||
* time (MTD write buffer size)
|
||||
|
|
Loading…
Reference in a new issue