From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753223AbdCORIu (ORCPT ); Wed, 15 Mar 2017 13:08:50 -0400 Received: from fllnx210.ext.ti.com ([198.47.19.17]:22856 "EHLO fllnx210.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751580AbdCORIC (ORCPT ); Wed, 15 Mar 2017 13:08:02 -0400 Subject: Re: [PATCH 1/2] UBI: Fix typos To: References: <20170105204450.12182-1-afd@ti.com> CC: From: "Andrew F. Davis" Message-ID: <7ec345e9-6efe-527e-57c5-e77362af774f@ti.com> Date: Wed, 15 Mar 2017 12:07:58 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170105204450.12182-1-afd@ti.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/05/2017 02:44 PM, Andrew F. Davis wrote: > Signed-off-by: Andrew F. Davis > --- > 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?