From: Aras Vaichas <arasv@magellan-technology.com>
To: MTD-LIST <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2+NAND problem in 2.6.13-at91
Date: Thu, 15 Sep 2005 11:46:29 +1000 [thread overview]
Message-ID: <4328D275.603@magellan-technology.com> (raw)
In-Reply-To: <432818D2.3080004@yandex.ru>
Artem B. Bityuckiy wrote:
> Aras Vaichas wrote:
>
>> Hi,
>>
>> I was previously using 2.6.12-rc1, AT91 with JFFS2 on NAND and I had no
>> problems whatsoever with using JFFS2 on NAND.
>
> This is the third report saying about the same problem, but the other two
> claimed that disabling summary helps, could you confirm this ? Or this is
> unrelated?
>
perhaps unrelated, and I can't find *any* summary options in my configuration
... can you be more specific? Do you mean EBS?
Aras
next prev parent reply other threads:[~2005-09-15 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 6:28 JFFS2+NAND problem in 2.6.13-at91 Aras Vaichas
2005-09-13 8:45 ` Aras Vaichas
2005-09-14 4:20 ` Aras Vaichas
2005-09-14 13:05 ` Timofei V. Bondarenko
2005-09-14 12:34 ` Artem B. Bityuckiy
2005-09-15 1:46 ` Aras Vaichas [this message]
2005-09-15 7:30 ` Artem B. Bityuckiy
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=4328D275.603@magellan-technology.com \
--to=arasv@magellan-technology.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