From: Vipin Kumar <vipin.kumar@st.com>
To: "Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.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, 4 Apr 2011 14:58:26 +0530 [thread overview]
Message-ID: <4D998F3A.1030109@st.com> (raw)
In-Reply-To: <1301907725.2760.45.camel@localhost>
On 4/4/2011 2:32 PM, Artem Bityutskiy wrote:
> 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".
>
OK. May be I misunderstood it...
This patch would not be needed for devices using the fixed hardware
And I thought since it is the hardware which is at fault, this patch is a
workaround, but yes, it may need a longer time to get fixed
Regards
Vipin
prev parent reply other threads:[~2011-04-04 9:28 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
2011-04-04 9:28 ` Vipin Kumar [this message]
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=4D998F3A.1030109@st.com \
--to=vipin.kumar@st.com \
--cc=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=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 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.