From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: actual mtd snapshot and jffs3 questions
Date: Thu, 23 Dec 2004 23:09:18 +0100 [thread overview]
Message-ID: <20041223220917.GC8918@ku-gbr.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0412231717520.4006@phoenix.infradead.org>
Am 2004-12-23 17:20 +0000 schrieb Artem B. Bityuckiy:
> > Indeed I have no CONFIG_JFFS3_FS_NAND nor CONFIG_JFFS3_FS_NOR_ECC but
> > the code required the members of the struct and compiled fine then.
> That are bugs introduced by newly added summary patch. Hope Ferenc will
> fix (may be after holydays).
Ok, he should take the time he needs, I will do other work meanwhile :)
> > which is right, no such file :) Forgot cvs add?
> Seems yes...
I forget this (I use svn) always and realize it when compiler breaks
with every new created file :)
> Strange. Will see. JFFS3 should mount JFFS2 images perfectly.
eheee! should :) But nice to have this cleared up...
Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
prev parent reply other threads:[~2004-12-23 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 14:51 actual mtd snapshot and jffs3 questions Konstantin Kletschke
2004-12-23 17:20 ` Artem B. Bityuckiy
2004-12-23 22:09 ` Konstantin Kletschke [this message]
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=20041223220917.GC8918@ku-gbr.de \
--to=lists@ku-gbr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox