On 01/05/2017 02:44 PM, Andrew F. Davis wrote: > Signed-off-by: Andrew F. Davis <[email protected]> > --- > drivers/mtd/ubi/Kconfig | 2 +- > drivers/mtd/ubi/io.c | 2 +- > drivers/mtd/ubi/ubi.h | 3 +-- > 3 files changed, 3 insertions(+), 4 deletions(-) > > diff --git a/drivers/mtd/ubi/Kconfig b/drivers/mtd/ubi/Kconfig > index f0855ce08ed9..43d131f5ae10 100644 > --- a/drivers/mtd/ubi/Kconfig > +++ b/drivers/mtd/ubi/Kconfig > @@ -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 > diff --git a/drivers/mtd/ubi/io.c b/drivers/mtd/ubi/io.c > index b6fb8f945c21..8290432017ce 100644 > --- a/drivers/mtd/ubi/io.c > +++ b/drivers/mtd/ubi/io.c > @@ -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. > * > diff --git a/drivers/mtd/ubi/ubi.h b/drivers/mtd/ubi/ubi.h > index 697dbcba7371..5fe62653995e 100644 > --- a/drivers/mtd/ubi/ubi.h > +++ b/drivers/mtd/ubi/ubi.h > @@ -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) >
Ping? These still apply to v4.11-rc1, does anyone take these trivial patches anymore?
