renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-25 05:34:00 +08:00
Code

UBI: Fix typos

Browse Source 
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
Andrew F. Davis 2017-01-05 14:44:49 -06:00 committed by Jiri Kosina
parent 12f54139d8
commit 2fae13124f
3 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/mtd/ubi/Kconfig
View File

@ -2,7 +2,7 @@ menuconfig MTD_UBI
tristate "Enable UBI - Unsorted block images" tristate "Enable UBI - Unsorted block images"
select CRC32 select CRC32
help 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 logical volumes on top of MTD devices, hides some complexities of
flash chips like wear and bad blocks and provides some other useful flash chips like wear and bad blocks and provides some other useful
capabilities. Please, consult the MTD web site for more details capabilities. Please, consult the MTD web site for more details

2
drivers/mtd/ubi/io.c
View File

@ -45,7 +45,7 @@
* About minimal I/O units. In general, UBI assumes flash device model where * 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, * 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 * 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 * (smaller) minimal I/O unit size for EC and VID headers to make it possible
* to do different optimizations. * to do different optimizations.
* *

3
drivers/mtd/ubi/ubi.h
View File

@ -544,8 +544,7 @@ struct ubi_debug_info {
* @vid_hdr_aloffset: starting offset of the VID header aligned to * @vid_hdr_aloffset: starting offset of the VID header aligned to
* @hdrs_min_io_size * @hdrs_min_io_size
* @vid_hdr_shift: contains @vid_hdr_offset - @vid_hdr_aloffset * @vid_hdr_shift: contains @vid_hdr_offset - @vid_hdr_aloffset
* @bad_allowed: whether the MTD device admits of bad physical eraseblocks or * @bad_allowed: whether the MTD device admits bad physical eraseblocks or not
* not
* @nor_flash: non-zero if working on top of NOR flash * @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 * @max_write_size: maximum amount of bytes the underlying flash can write at a
* time (MTD write buffer size) * time (MTD write buffer size)