From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: "Anurag Raghavan (RBEI/ETW11)" <Raghavan.Anurag@in.bosch.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Bad block Management Patch
Date: Tue, 24 Jan 2017 08:58:10 +0100 [thread overview]
Message-ID: <20170124085810.29afbfaf@bbrezillon> (raw)
In-Reply-To: <8aa988fcc46c480d863cf4ee2ef40b2c@SGPMBX1023.APAC.bosch.com>
On Tue, 24 Jan 2017 04:56:47 +0000
"Anurag Raghavan (RBEI/ETW11)" <Raghavan.Anurag@in.bosch.com> wrote:
> Hi Boris,
>
>
> I am using kernel version-3.0.35
> I am facing uncorrectable ECC error in ubifs. I am suspecting, it is because of bad blocks are not properly handled in my driver.
> Is there any patches available to handle the bad block in the specified version...
Is this a joke? Now you're not even adding the mailing list in Cc, and
you keep giving too few information (I don't even remember what's your
NAND controller).
I suggested that you test a mainline kernel, and you keep asking for
patches on top of a really old kernel. And by the way, don't expect us
to do your job (you can use git log and try to apply the patches that
seem relevant to you, but I clearly won't do that for you).
So please stop asking us to fix your bugs unless you start listening to
our suggestions, and the first one is to try a newer kernel (4.9 for
example).
Thanks,
Boris
next prev parent reply other threads:[~2017-01-24 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 4:56 [OpenRISC] Bad block Management Patch Anurag Raghavan
2017-01-24 4:56 ` Anurag Raghavan (RBEI/ETW11)
2017-01-24 4:56 ` Anurag Raghavan (RBEI/ETW11)
2017-01-24 7:58 ` Boris Brezillon [this message]
2017-01-24 8:11 ` Richard Weinberger
-- strict thread matches above, loose matches on Subject: below --
2017-01-24 7:02 Anurag Raghavan (RBEI/ETW11)
2017-01-24 7:09 ` Greg KH
2017-01-24 7:15 ` Anurag Raghavan (RBEI/ETW11)
2017-01-24 7:38 ` Greg KH
2017-01-24 4:56 Anurag Raghavan (RBEI/ETW11)
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=20170124085810.29afbfaf@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=Raghavan.Anurag@in.bosch.com \
--cc=linux-mtd@lists.infradead.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 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.