From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-mtd@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Mark Vasut <marek.vasut@gmail.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
tharvey@gateworks.com, stable <stable@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] ubi: Reject MLC NAND
Date: Thu, 08 Mar 2018 17:01:15 +0200 [thread overview]
Message-ID: <1520521275.20980.41.camel@gmail.com> (raw)
In-Reply-To: <3797589.z8fAhu5iDP@blindfold>
On Thu, 2018-03-08 at 15:43 +0100, Richard Weinberger wrote:
> As stated by David Woodhouse, it was a huge mistake by UBI to not
> reject MLC
> NAND from the very beginning.
Correction: when we were developing UBI/UBIFS and upstreamed them, MLC
was widely used yet we did not really know about it. So there was
nothing to reject yet.
The mistake is that we did not add the reject timely. When people
started reporting MLC issues we were answering that UBI/UBIFS stack
needs more work to make MLC safe to use, and we hoped someone would do
the work.
Artem.
next prev parent reply other threads:[~2018-03-08 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 10:45 [PATCH] ubi: Reject MLC NAND Richard Weinberger
2018-03-04 19:46 ` Boris Brezillon
2018-03-06 23:18 ` Pavel Machek
2018-03-07 1:57 ` David Oberhollenzer
2018-03-07 8:01 ` Richard Weinberger
2018-03-07 15:24 ` Artem Bityutskiy
2018-03-07 21:43 ` Pavel Machek
2018-03-07 22:08 ` Steve deRosier
2018-03-07 22:11 ` David Woodhouse
2018-03-07 22:17 ` Pavel Machek
2018-03-07 22:30 ` Boris Brezillon
2018-03-07 23:27 ` Willy Tarreau
2018-03-07 22:40 ` Boris Brezillon
2018-03-08 13:42 ` Linus Walleij
2018-03-08 14:43 ` Richard Weinberger
2018-03-08 15:01 ` Artem Bityutskiy [this message]
2018-03-08 15:28 ` Richard Weinberger
2018-03-08 15:34 ` Artem Bityutskiy
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=1520521275.20980.41.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=tharvey@gateworks.com \
--cc=ulf.hansson@linaro.org \
/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