From: tglx@linutronix.de (Thomas Gleixner)
To: Dmitry Konyshev <dmitry.konyshev@auriga.ru>,
linux-mtd@lists.infradead.org
Subject: Re: nand bug
Date: Tue, 27 Apr 2004 22:45:54 +0200 [thread overview]
Message-ID: <200404272245.54879.tglx@linutronix.de> (raw)
In-Reply-To: <408E752B.5010802@auriga.ru>
On Tuesday 27 April 2004 16:58, Dmitry Konyshev wrote:
> Hi everybody,
>
> nand_erase doesn't invalidate pagebuf member of nand_chip struct. It
> causes data incoherence.
>
> wbr, Dmitry.
Thanks. I will fix it tomorrow.
--
Thomas
________________________________________________________________________
"Free software" is a matter of liberty, not price. To understand the concept,
you should think of "free" as in "free speech,'' not as in "free beer".
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2004-04-27 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 14:58 nand bug Dmitry Konyshev
2004-04-27 20:45 ` Thomas Gleixner [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=200404272245.54879.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=dmitry.konyshev@auriga.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox