From: Richard Weinberger <richard.weinberger@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: "Anurag Raghavan (RBEI/ETW11)" <Raghavan.Anurag@in.bosch.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Bad block Management Patch
Date: Tue, 24 Jan 2017 09:11:17 +0100 [thread overview]
Message-ID: <CAFLxGvw1UfFYQU7G3J_E=as5Y=rxDGJwFOTVz4=grTOQy-nmzQ@mail.gmail.com> (raw)
In-Reply-To: <20170124085810.29afbfaf@bbrezillon>
Raghavan Anurag,
On Tue, Jan 24, 2017 at 8:58 AM, Boris Brezillon
<boris.brezillon@free-electrons.com> wrote:
> 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...
This is not how community support works.
He happily help with recent kernels but debugging problems on
outdated kernels with vendor patches applied is out of scope.
What you expect from us is hard and takes a lot of time, we cannot
do that for free in our spare time.
--
Thanks,
//richard
next prev parent reply other threads:[~2017-01-24 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 4:56 Bad block Management Patch Anurag Raghavan (RBEI/ETW11)
2017-01-24 4:56 ` [OpenRISC] " Anurag Raghavan
2017-01-24 4:56 ` Anurag Raghavan (RBEI/ETW11)
2017-01-24 7:58 ` Boris Brezillon
2017-01-24 8:11 ` Richard Weinberger [this message]
-- 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='CAFLxGvw1UfFYQU7G3J_E=as5Y=rxDGJwFOTVz4=grTOQy-nmzQ@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=Raghavan.Anurag@in.bosch.com \
--cc=boris.brezillon@free-electrons.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.