public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: ext Viresh Kumar <viresh.kumar@st.com>
Cc: Vipin Kumar <vipin.kumar@st.com>,
	David.Woodhouse@intel.com, amit.goel@st.com,
	armando.visconti@st.com, shiraz.hashim@st.com,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH resend] Newly erased page read workaround
Date: Fri, 01 Apr 2011 14:30:48 +0300	[thread overview]
Message-ID: <1301657448.2789.44.camel@localhost> (raw)
In-Reply-To: <1301653534-22223-1-git-send-email-viresh.kumar@st.com>

On Fri, 2011-04-01 at 15:55 +0530, ext Viresh Kumar wrote:
> +		/*
> +		 * This is a temporary erase check. A newly erased page read
> +		 * would result in an ecc error because the oob data is also
> +		 * erased to FF and the calculated ecc for an FF data is not
> +		 * FF..FF.
> +		 * This is a workaround to skip performing correction in case
> +		 * data is FF..FF
> +		 */

Sorry, but still questions.

The comment says this is temporary - why? When and how this going to be
change to become "permanent".

And you still did not add words about the problem with bit-flips.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2011-04-01 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 10:25 [PATCH resend] Newly erased page read workaround Viresh Kumar
2011-04-01 11:30 ` Artem Bityutskiy [this message]
2011-04-01 11:42   ` Vipin Kumar
2011-04-01 11:44     ` Artem Bityutskiy
2011-04-04  5:45       ` Vipin Kumar
2011-04-04  6:27         ` Artem Bityutskiy
2011-04-04  9:00           ` Vipin Kumar
2011-04-04  9:02             ` Artem Bityutskiy
2011-04-04  9:28               ` Vipin Kumar

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=1301657448.2789.44.camel@localhost \
    --to=artem.bityutskiy@nokia.com \
    --cc=David.Woodhouse@intel.com \
    --cc=amit.goel@st.com \
    --cc=armando.visconti@st.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shiraz.hashim@st.com \
    --cc=vipin.kumar@st.com \
    --cc=viresh.kumar@st.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