From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>, Pavel Machek <pavel@ucw.cz>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
cyrille.pitchen@wedev4u.fr, marek.vasut@gmail.com,
boris.brezillon@free-electrons.com, computersforpeace@gmail.com,
dwmw2@infradead.org, tharvey@gateworks.com,
stable@vger.kernel.org
Subject: Re: [PATCH] ubi: Reject MLC NAND
Date: Wed, 07 Mar 2018 17:24:23 +0200 [thread overview]
Message-ID: <1520436263.2674.35.camel@gmail.com> (raw)
In-Reply-To: <6772577.AmT7QaWTNU@blindfold>
On Wed, 2018-03-07 at 09:01 +0100, Richard Weinberger wrote:
> Pavel,
>
> Am Mittwoch, 7. März 2018, 00:18:05 CET schrieb Pavel Machek:
> > On Sat 2018-03-03 11:45:54, Richard Weinberger wrote:
> > > While UBI and UBIFS seem to work at first sight with MLC NAND,
> > > you will
> > > most likely lose all your data upon a power-cut or due to
> > > read/write
> > > disturb.
> > > In order to protect users from bad surprises, refuse to attach to
> > > MLC
> > > NAND.
> > >
> > > Cc: stable@vger.kernel.org
> >
> > That sounds like _really_ bad idea for stable. All it does is it
> > removes support for hardware that somehow works.
>
> MLC is not supported and does not work. Full stop.
Ack.
next prev parent reply other threads:[~2018-03-07 15:24 UTC|newest]
Thread overview: 21+ 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 8:01 ` Richard Weinberger
2018-03-07 15:24 ` Artem Bityutskiy [this message]
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 14:43 ` Richard Weinberger
2018-03-08 15:01 ` Artem Bityutskiy
2018-03-08 15:28 ` Richard Weinberger
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=1520436263.2674.35.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=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=pavel@ucw.cz \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=tharvey@gateworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.