From: Wolfgang Denk <wd@denx.de>
To: David Ho <davidkwho@gmail.com>
Cc: David Jander <david.jander@protonic.nl>, linuxppc-embedded@ozlabs.org
Subject: Re: How reliable is jffs2 really (denx cvs devel kernel)?
Date: Tue, 19 Jul 2005 20:42:41 +0200 [thread overview]
Message-ID: <20050719184241.78430352671@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 19 Jul 2005 08:57:20 EDT." <4dd15d1805071905573ebcba61@mail.gmail.com>
In message <4dd15d1805071905573ebcba61@mail.gmail.com> you wrote:
>
> I updated the JFFS2 portion of the Denx devel kernel with the latest
> from CVS and it solved the initial mount time problem. But it was a
> while a ago when I did this. Both the devel kernel and the CVS head
> has changed quite a bit since then.
I would rally appreciate if you mentioned which exact version of the
kernel you are talking about. "The Denx devel kernel" can be anything
- either yesterday or 3 years old.
At the moment our CVS tree contains a snapshot from MTD CVS of March
13, 2005; yes, we did the necessary backport to the 2.4 kernel.
Do you want to say that this version still has mount time issues?
Please provide details!
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The word "fit", as I understand it, means "appropriate to a purpose",
and I would say the body of the Dean is supremely appropriate to the
purpose of sitting around all day and eating big heavy meals.
- Terry Pratchett, _Moving Pictures_
next prev parent reply other threads:[~2005-07-19 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 8:21 How reliable is jffs2 really (denx cvs devel kernel)? David Jander
2005-07-19 12:57 ` David Ho
2005-07-19 18:42 ` Wolfgang Denk [this message]
2005-07-19 19:03 ` David Ho
2005-07-19 18:37 ` Wolfgang Denk
2005-07-20 6:30 ` David Jander
2005-07-20 8:37 ` Wolfgang Denk
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=20050719184241.78430352671@atlas.denx.de \
--to=wd@denx.de \
--cc=david.jander@protonic.nl \
--cc=davidkwho@gmail.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).