From: David Woodhouse <dwmw2@infradead.org>
To: Eric Nelson <eric_n2@verifone.com>
Cc: brendan.simon@bigpond.com, linux-mtd@lists.infradead.org
Subject: Re: DOC2000 partitiioning question
Date: Wed, 12 Jun 2002 11:47:50 +0100 [thread overview]
Message-ID: <24980.1023878870@redhat.com> (raw)
In-Reply-To: <614CC7C21856D1118DA30060B06B487302ACCA37@SMF-NT-MAIL1>
I discarded your message at first because I couldn't find any original
content. It's customary to quote only the relevant part of the message to
which you're replying, with a suitable marker such as '> ' to distinguish
it from your own text.
eric_n2@verifone.com said:
> I know, from following this list, that there are many, like me, who
> have no choice but to use DOC, and are sold on JFFS2, but just don't
> have the time or expertise to make these modifications. I know you
> are busy, but you are the expert, and it would be widely appreciated
> if you lend your expertise to finishing porting JFFS2 to DOC, so I,
> and many others, could quit telling our bosses that JFFS2 is
> definitely the best, but it's not quite ready for DOC??
It's getting there, slowly. I dispute the implication that I'm the only
person with sufficient expertise -- Thomas has done a very good job of
implementing most of the NAND support, for example.
I don't have much time either -- certainly not enough to set up the hardware
and run tests on it. But I _can_ find some time occasionally to work on it
if someone tests it and points out problems.
The thing is -- I haven't received any failure reports for NAND flash
recently. That either means it's perfect or it means nobody cares enough to
even test it.
The only way it's going to progress from the "I think it works, wouldn't
want to ship it yet" state to "Ready for production", even if the code
itself is actually perfect already, is by getting tested hard.
That means either someone out there getting off their proverbial wossname
and testing it, reporting the results to my satisfaction, or me getting
assigned sufficient time to do it. I was sort of hoping the former was more
likely -- because the latter isn't.
--
dwmw2
next prev parent reply other threads:[~2002-06-12 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 20:44 DOC2000 partitiioning question Eric Nelson
2002-06-12 10:47 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-11 3:53 Brendan J Simon
2002-06-11 7:06 ` David Woodhouse
2002-06-11 7:38 ` Brendan J Simon
2002-06-11 8:45 ` 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=24980.1023878870@redhat.com \
--to=dwmw2@infradead.org \
--cc=brendan.simon@bigpond.com \
--cc=eric_n2@verifone.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