From: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd/ubi: fix initialization order of ubi subsystems
Date: Fri, 21 Jun 2019 22:41:39 +0300 [thread overview]
Message-ID: <20190621224139.48fa0537@laska.lan> (raw)
In-Reply-To: <1524034294.13675.1561145581382.JavaMail.zimbra@nod.at>
On Fri, 21 Jun 2019 21:33:01 +0200 (CEST)
Richard Weinberger <richard@nod.at> wrote:
> ----- Ursprüngliche Mail -----
> >> > PS we send the same patch to u-boot.
> >>
> >> In u-boot the story is a little different because it has no concept of
> >> threads and executes work immediately.
> >>
> >> Do you see this on a recent u-boot?
> >> With this commit in u-boot this problem should not happen:
> >> f82290afc847 ("mtd: ubi: Fix worker handling")
> >
> > no we use 201.07 based bootloader. I'll look on it. Thanks.
>
> Please backport the said fix and communicate this on the
> u-boot mailinglist.
>
> Your patch fixes the issue only partially, you will still face
> issues if ubi sees bitflips at attach time.
thanks a lot.
> Thanks,
> //richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-06-21 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 13:27 [PATCH] mtd/ubi: fix initialization order of ubi subsystems Mikhail Kshevetskiy
2019-06-21 16:04 ` Artem Bityutskiy
2019-06-21 17:26 ` Richard Weinberger
2019-06-21 18:39 ` Mikhail Kshevetskiy
2019-06-21 18:47 ` Richard Weinberger
2019-06-21 19:16 ` Mikhail Kshevetskiy
2019-06-21 19:33 ` Richard Weinberger
2019-06-21 19:41 ` Mikhail Kshevetskiy [this message]
2019-06-21 19:16 ` Mikhail Kshevetskiy
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=20190621224139.48fa0537@laska.lan \
--to=mikhail.kshevetskiy@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.