From: Tanya Brokhman <tlinder@codeaurora.org>
To: Richard Weinberger <richard@nod.at>, dedekind1@gmail.com
Cc: linux-arm-msm@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling
Date: Sun, 02 Nov 2014 19:18:00 +0200 [thread overview]
Message-ID: <54566748.3020208@codeaurora.org> (raw)
In-Reply-To: <54566396.1050209@nod.at>
On 11/2/2014 7:02 PM, Richard Weinberger wrote:
> Am 02.11.2014 um 15:12 schrieb Tanya Brokhman:
>>> Back to topic.
>>> Storing the read-counters into fastmap also not a good idea because the fastmap can get lost completely (by design).
>>
>> yes,I'm aware of that. We have a default value for that case, and we're trying to avoid fastmap being invalid...
>
> Here be dragons. Can you please share these modifications?
nothing to share yet :) work in progress. more thought then code at this
point. will share as soon as have something valid...
>
> Thanks,
> //richard
>
Thanks,
Tanya Brokhman
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-11-02 17:18 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 13:49 [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling Tanya Brokhman
2014-10-26 13:49 ` Tanya Brokhman
2014-10-26 20:39 ` Richard Weinberger
2014-10-26 20:39 ` Richard Weinberger
2014-10-27 8:41 ` Tanya Brokhman
2014-10-27 8:41 ` Tanya Brokhman
2014-10-27 8:56 ` Richard Weinberger
2014-10-27 8:56 ` Richard Weinberger
2014-10-29 11:03 ` Tanya Brokhman
2014-10-29 12:00 ` Richard Weinberger
2014-10-31 13:12 ` Tanya Brokhman
2014-10-31 15:34 ` Richard Weinberger
2014-10-31 15:39 ` Richard Weinberger
2014-10-31 22:55 ` Jeff Lauruhn (jlauruhn)
2014-11-02 13:30 ` Tanya Brokhman
2014-11-07 9:21 ` Artem Bityutskiy
2014-11-07 9:21 ` Artem Bityutskiy
2014-11-02 13:25 ` Tanya Brokhman
2014-11-06 8:07 ` Artem Bityutskiy
2014-11-06 8:07 ` Artem Bityutskiy
2014-11-06 12:16 ` Tanya Brokhman
2014-11-07 8:55 ` Artem Bityutskiy
2014-11-07 8:58 ` Artem Bityutskiy
2014-11-11 20:36 ` Tanya Brokhman
2014-11-11 20:36 ` Tanya Brokhman
2014-11-11 21:39 ` Richard Weinberger
2014-11-11 21:39 ` Richard Weinberger
2014-11-12 12:07 ` Artem Bityutskiy
2014-11-12 12:07 ` Artem Bityutskiy
2014-11-12 13:01 ` Richard Weinberger
2014-11-12 13:01 ` Richard Weinberger
2014-11-12 13:32 ` Artem Bityutskiy
2014-11-12 13:32 ` Artem Bityutskiy
2014-11-12 15:37 ` Richard Weinberger
2014-11-12 15:37 ` Richard Weinberger
2014-11-12 11:55 ` Artem Bityutskiy
2014-11-12 11:55 ` Artem Bityutskiy
2014-11-13 12:13 ` Tanya Brokhman
2014-11-13 12:13 ` Tanya Brokhman
2014-11-13 13:36 ` Artem Bityutskiy
2014-11-13 13:36 ` Artem Bityutskiy
2014-11-23 8:13 ` Tanya Brokhman
2014-11-23 8:13 ` Tanya Brokhman
2014-11-02 13:23 ` Tanya Brokhman
2014-11-02 13:54 ` Richard Weinberger
2014-11-02 14:12 ` Tanya Brokhman
2014-11-02 17:02 ` Richard Weinberger
2014-11-02 17:18 ` Tanya Brokhman [this message]
[not found] <201411101307.03225.jbe@pengutronix.de>
2014-11-10 12:35 ` Richard Weinberger
2014-11-10 13:12 ` Juergen Borleis
2014-11-11 9:23 ` Richard Weinberger
2014-11-10 13:13 ` Ricard Wanderlof
2014-11-10 13:42 ` Juergen Borleis
2014-11-10 13:52 ` Ricard Wanderlof
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=54566748.3020208@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=dedekind1@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--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.