From: Richard Weinberger <richard@nod.at>
To: Bang Li <libang.linuxer@gmail.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] mtdblock: tolerate corrected bit-flips
Date: Tue, 28 Mar 2023 18:51:56 +0200 (CEST) [thread overview]
Message-ID: <1646372169.361736.1680022316353.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20230328163012.4264-1-libang.linuxer@gmail.com>
----- Ursprüngliche Mail -----
> Von: "Bang Li" <libang.linuxer@gmail.com>
> An: "Miquel Raynal" <miquel.raynal@bootlin.com>, "richard" <richard@nod.at>, "Vignesh Raghavendra" <vigneshr@ti.com>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>, "linux-kernel" <linux-kernel@vger.kernel.org>, "Bang Li"
> <libang.linuxer@gmail.com>, "stable" <stable@vger.kernel.org>
> Gesendet: Dienstag, 28. März 2023 18:30:12
> Betreff: [PATCH v2] mtdblock: tolerate corrected bit-flips
> mtd_read() may return -EUCLEAN in case of corrected bit-flips.This
> particular condition should not be treated like an error.
>
> Signed-off-by: Bang Li <libang.linuxer@gmail.com>
> Fixes: e47f68587b82 ("mtd: check for max_bitflips in mtd_read_oob()")
> Cc: <stable@vger.kernel.org> # v3.7
> ---
Acked-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-03-28 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:30 [PATCH v2] mtdblock: tolerate corrected bit-flips Bang Li
2023-03-28 16:51 ` Richard Weinberger [this message]
2023-04-03 15:59 ` Miquel Raynal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1646372169.361736.1680022316353.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=libang.linuxer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=stable@vger.kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox