From: David Vrabel <dvrabel@arcom.com>
To: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: kernel oops in cfi_cmdset_0002.c:do_write_one()...
Date: Tue, 13 Apr 2004 12:04:51 +0100 [thread overview]
Message-ID: <407BC953.2060005@arcom.com> (raw)
In-Reply-To: <1081514570.20197.182.camel@imladris.demon.co.uk>
> 1. Wait till the MTD CVS code is actually stable. It's not at the
> moment; cfi_cmdset_0002.c is known to be broken and I can't send it
> off while it's like that.
Revert cfi_cmdset_0002.c back to 1.94? 1.95 is the change that appears
to have broken interleaved chips.
David
next prev parent reply other threads:[~2004-04-13 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 15:43 kernel oops in cfi_cmdset_0002.c:do_write_one() Steven Scholz
2004-04-07 16:19 ` Thayne Harbaugh
2004-04-07 16:47 ` David Vrabel
2004-04-11 11:40 ` Steven Scholz
2004-04-08 7:16 ` Steven Scholz
2004-04-08 13:29 ` Steven Scholz
2004-04-08 14:37 ` Jörn Engel
2004-04-08 19:28 ` Thomas Gleixner
2004-04-08 19:47 ` Jörn Engel
2004-04-09 12:42 ` David Woodhouse
2004-04-13 9:31 ` Jörn Engel
2004-04-13 14:28 ` David Woodhouse
2004-04-13 11:04 ` David Vrabel [this message]
[not found] <D73A25AA6E54D511AD74009027B1110F5BB16A@ORION>
2004-04-07 16:12 ` Steven Scholz
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=407BC953.2060005@arcom.com \
--to=dvrabel@arcom.com \
--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