From: Richard Weinberger <richard.weinberger@gmail.com>
To: Sergeant Peppercorn <speppercorn109@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS ECC errors
Date: Tue, 13 Aug 2019 23:35:26 +0200 [thread overview]
Message-ID: <CAFLxGvwn7j5Pttac-V_6o7dtRt=i39UrZPP=adNEB54PRej8xA@mail.gmail.com> (raw)
In-Reply-To: <CAMxq0fOJ0uqqzPRW_wBiAZS=KzpRy_waGHODErhjcLgRbX5ALQ@mail.gmail.com>
On Wed, Aug 7, 2019 at 6:52 PM Sergeant Peppercorn
<speppercorn109@gmail.com> wrote:
>
> Also, would this apply fo my 4.9.88 IMX kernel as well as the TI 3.12.10 kernel?
We care only about mainline, sorry.
> On Wed, Aug 7, 2019 at 9:51 AM Sergeant Peppercorn
> <speppercorn109@gmail.com> wrote:
> >
> > Hi, so are you saying that I should try to merge in these two commits
> > for a proper fix for this?
> > 730a43fbc135 ("mtd: nand: add nand_check_erased helper functions")
> > fdf2e8210529 ("mtd: nand: gpmi: Fix failure when a erased page has a
> > bitflip at BBM")
No. I said you need most likely 730a43fbc135 and commits it depends on.
Commit fdf2e8210529 was just an example of a related bug.
> > I am assuming these are from the mainline kernel?
Sure.
> > If not, how do I fix this? this other patch, instead or with those two commits?
> > http://lists.infradead.org/pipermail/linux-mtd/2014-January/051357.html
> >
> > The patch doesn't seem to be able to apply cleanly to my kernel so I
> > must do some deep merging. I have not looked for the two commits yet.
This patch was AFAIK not applied because we decided to work around the issue
in NAND core.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-08-13 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 16:24 UBIFS ECC errors Sergeant Peppercorn
2019-08-01 8:03 ` Richard Weinberger
2019-08-02 16:14 ` Sergeant Peppercorn
2019-08-03 8:48 ` Richard Weinberger
2019-08-05 21:35 ` Sergeant Peppercorn
2019-08-07 16:51 ` Sergeant Peppercorn
2019-08-07 16:52 ` Sergeant Peppercorn
2019-08-13 21:35 ` Richard Weinberger [this message]
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='CAFLxGvwn7j5Pttac-V_6o7dtRt=i39UrZPP=adNEB54PRej8xA@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=speppercorn109@gmail.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;
as well as URLs for NNTP newsgroup(s).