From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Vipin Kumar <vipin.kumar@st.com>
Cc: Viresh KUMAR <viresh.kumar@st.com>,
"David.Woodhouse@intel.com" <David.Woodhouse@intel.com>,
Shiraz HASHIM <shiraz.hashim@st.com>, amitgoel <amit.goel@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH resend] Newly erased page read workaround
Date: Mon, 04 Apr 2011 12:02:05 +0300 [thread overview]
Message-ID: <1301907725.2760.45.camel@localhost> (raw)
In-Reply-To: <4D9988A1.1030405@st.com>
On Mon, 2011-04-04 at 14:30 +0530, Vipin Kumar wrote:
> On 4/4/2011 11:57 AM, Artem Bityutskiy wrote:
> > On Mon, 2011-04-04 at 11:15 +0530, ext Vipin Kumar wrote:
> >> On 4/1/2011 5:14 PM, Artem Bityutskiy wrote:
> >>> On Fri, 2011-04-01 at 17:12 +0530, ext Vipin Kumar wrote:
> >>>> Temporary because the fsmc peripheral itself needs a fix for this problem
> >>>
> >>> Do you mean a hardware fix?
> >>>
> >> Ideally speaking, Yes
> >
> > Then the comment is not saying the truth I think - this solution is
> > permanent.
> >
>
> That's why it is a workaround
> I thought "workaround" says it all
I thought we were talking about word "temporary". Temporary means "will
be fixed very very soon".
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-04 9:04 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
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 [this message]
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=1301907725.2760.45.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