From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.bootlin.com ([62.4.15.54]) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1fXQj3-0001CN-5O for linux-mtd@lists.infradead.org; Mon, 25 Jun 2018 12:36:31 +0000 Date: Mon, 25 Jun 2018 14:35:57 +0200 From: Miquel Raynal To: Boris Brezillon Cc: Richard Weinberger , linux-mtd@lists.infradead.org, David Woodhouse , Brian Norris , Marek Vasut Subject: Re: [PATCH] mtd: rawnand: micron: Update ecc_stats.corrected Message-ID: <20180625143557.29d52b59@xps13> In-Reply-To: <20180620100444.4f60f8dd@bbrezillon> References: <20180620074443.30235-1-boris.brezillon@bootlin.com> <20180620095843.7ec30e67@xps13> <20180620100444.4f60f8dd@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Boris, On Wed, 20 Jun 2018 10:04:44 +0200, Boris Brezillon wrote: > On Wed, 20 Jun 2018 09:58:43 +0200 > Miquel Raynal wrote: >=20 > > Hi Boris, > >=20 > > On Wed, 20 Jun 2018 09:44:43 +0200, Boris Brezillon > > wrote: > > =20 > > > Even if we can't update ecc_stats.corrected with an accurate value we > > > should at least increase the number of bitflips so that MTD users can > > > know that there was some bitflips. > > >=20 > > > Just add chip->ecc.strength to mtd->ecc_stats.corrected which should > > > account for the worst case situation. > > >=20 > > > Signed-off-by: Boris Brezillon > > > --- =20 > >=20 > > Shouldn't we consider this change as a fix? =20 >=20 > It's not really fixing a bug, in that ecc_stats.corrected are already > not accurate, they just give a hint about how often you fix bitflips > on a NAND device. But if you think it should be backported, I can add > the Fixes and Cc-stable tags. >=20 It's fine for me. Applied to nand/next. Thanks, Miqu=C3=A8l