From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_scan_eraseblock() - errors
Date: Wed, 31 Jul 2002 12:45:52 +0100 [thread overview]
Message-ID: <2881.1028115952@redhat.com> (raw)
In-Reply-To: <20020731103419.GA23749@wohnheim.fh-wedel.de>
joern@wohnheim.fh-wedel.de said:
> How exactly is this done? On the next mount after the failed write?
> By toggling bits in the status word of the node header?
By marking it obsolete. It's an optimisation.
> If so, this will not work with any of the shiny STMicro chips with
> hardware ECC, so I would have to tackle that one too, once we merge.
Doesn't matter. Our other plans for deferring CRC checking will avoid the
harmless complaint.
--
dwmw2
next prev parent reply other threads:[~2002-07-31 11:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 18:11 jffs2_scan_eraseblock() - errors Curtis, Allen
2002-07-30 22:21 ` David Woodhouse
2002-07-31 10:34 ` Jörn Engel
2002-07-31 11:45 ` David Woodhouse [this message]
2002-07-31 11:57 ` Jörn Engel
2002-07-31 11:59 ` David Woodhouse
2002-07-31 12:16 ` Jörn Engel
2002-07-31 12:17 ` David Woodhouse
2002-07-31 13:07 ` Jörn Engel
2002-07-31 21:12 ` Problems with full FS Joakim Tjernlund
2002-08-01 18:26 ` Oops when unlinking stale file Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 23:30 jffs2_scan_eraseblock() - errors Curtis, Allen
2002-07-30 23:42 ` David Woodhouse
2002-07-30 23:59 Curtis, Allen
2002-07-31 0:15 ` David Woodhouse
2002-07-31 0:18 ` David Woodhouse
2002-07-31 0:38 Curtis, Allen
2002-07-31 0:48 ` David Woodhouse
2002-07-31 1:15 Curtis, Allen
2002-07-31 3:07 ` David Woodhouse
2002-07-31 23:02 Curtis, Allen
2002-08-01 10:44 ` David Woodhouse
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=2881.1028115952@redhat.com \
--to=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--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 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.