tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
fork atom

UBI: Fix typos

Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>

authored by

Andrew F. Davis and committed by
Jiri Kosina 2fae1312 12f54139

+3 -4
+1 -1
drivers/mtd/ubi/Kconfig
··· 2 2 tristate "Enable UBI - Unsorted block images" 3 3 select CRC32 4 4 help 5 - UBI is a software layer above MTD layer which admits of LVM-like 5 + UBI is a software layer above MTD layer which admits use of LVM-like 6 6 logical volumes on top of MTD devices, hides some complexities of 7 7 flash chips like wear and bad blocks and provides some other useful 8 8 capabilities. Please, consult the MTD web site for more details
+1 -1
drivers/mtd/ubi/io.c
··· 45 45 * About minimal I/O units. In general, UBI assumes flash device model where 46 46 * there is only one minimal I/O unit size. E.g., in case of NOR flash it is 1, 47 47 * in case of NAND flash it is a NAND page, etc. This is reported by MTD in the 48 - * @ubi->mtd->writesize field. But as an exception, UBI admits of using another 48 + * @ubi->mtd->writesize field. But as an exception, UBI admits use of another 49 49 * (smaller) minimal I/O unit size for EC and VID headers to make it possible 50 50 * to do different optimizations. 51 51 *
+1 -2
drivers/mtd/ubi/ubi.h
··· 544 544 * @vid_hdr_aloffset: starting offset of the VID header aligned to 545 545 * @hdrs_min_io_size 546 546 * @vid_hdr_shift: contains @vid_hdr_offset - @vid_hdr_aloffset 547 - * @bad_allowed: whether the MTD device admits of bad physical eraseblocks or 548 - * not 547 + * @bad_allowed: whether the MTD device admits bad physical eraseblocks or not 549 548 * @nor_flash: non-zero if working on top of NOR flash 550 549 * @max_write_size: maximum amount of bytes the underlying flash can write at a 551 550 * time (MTD write buffer size)