From: Vipin Malik <vipin.malik@daniel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: jffs-dev <jffs-dev@axis.com>, mtd <mtd@infradead.org>
Subject: 5031 cycles and counting...
Date: Mon, 23 Apr 2001 09:41:46 -0500 [thread overview]
Message-ID: <3AE43F2A.1A1C8BA2@daniel.com> (raw)
5031 async power fail cycles and counting since the last problem (and
fix).
Nice. And good work David :)
Strictly personally speaking, I would be now be happy to put this into a
production system.
Vipin
NOTICE FOR THE PUBLIC AT LARGE:
As usual, for the benefit for the lawsuit happy, no claim regarding any
suitability for any purpose, either expressed or
implied is being made regarding any thing. If you have a particular DNA
strain (usually found in inhabitants of a particularly large north
American country),
that prompts you to call your lawyer at the drop of a hat (or usually
after your own mistake that you find yourself unable to correct
and at a loss), please disregard this message.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
reply other threads:[~2001-04-23 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AE43F2A.1A1C8BA2@daniel.com \
--to=vipin.malik@daniel.com \
--cc=dwmw2@infradead.org \
--cc=jffs-dev@axis.com \
--cc=mtd@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