public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "tong changda" <tongcd@hotmail.com>
To: joern@wohnheim.fh-wedel.de
Cc: dedekind@yandex.ru, linux-mtd@lists.infradead.org,
	munira.ahmed@radixs.com
Subject: Re: jffs2 corrupt rarely, how to fix it?
Date: Tue, 14 Jun 2005 08:44:03 +0800	[thread overview]
Message-ID: <BAY7-F32F576C95CF56BEF0F5611DAF30@phx.gbl> (raw)
In-Reply-To: <20050613072709.GB26966@wohnheim.fh-wedel.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 1209 bytes --]

Thanks, one last question
After I had porting the mtd/jffs2 code, how to confirm that the problem is 
fixed? That is, Is there some ways to make these bugs to be more easily 
appeared on arm-linux-2.4.19/20?

>From: Jörn Engel <joern@wohnheim.fh-wedel.de>
>To: tong changda <tongcd@hotmail.com>
>CC: munira.ahmed@radixs.com, 
dedekind@yandex.ru,linux-mtd@lists.infradead.org
>Subject: Re: jffs2 corrupt rarely, how to fix it?
>Date: Mon, 13 Jun 2005 09:27:09 +0200
>
>On Mon, 13 June 2005 10:23:28 +0800, tong changda wrote:
> >
> > Seem a little hard for me
> > I guess all changeset for jffs2 is limited in fs/jffs2/. the interface 
with
> > mtd should keep unchanged, If so, is it easier to start from 
linux-2.4.31
> > instead of 2.6.11.11?
>
>Most likely.  It should still be quite a bit of work.  An mtd update
>once caused people to claim that I effectively updated our kernel.  It
>pulled in quite a bit from header files that didn't exist in the old
>kernel, etc.
>
>Jörn
>
>--
>And spam is a useful source of entropy for /dev/random too!
>-- Jasmine Strong

_________________________________________________________________
ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger:  http://messenger.msn.com/cn  

  reply	other threads:[~2005-06-14  1:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10  2:23 jffs2 corrupt rarely, how to fix it? tong changda
2005-06-10  8:03 ` Artem B. Bityuckiy
2005-06-10  8:14   ` Munira Ahmed
2005-06-10  8:24     ` Artem B. Bityuckiy
2005-06-10 11:21     ` Jörn Engel
2005-06-13  2:23       ` tong changda
2005-06-13  7:27         ` Jörn Engel
2005-06-14  0:44           ` tong changda [this message]
2005-06-14  9:29             ` Jörn Engel
2005-06-14 10:01               ` Munira Ahmed
2005-06-14 13:19                 ` David Woodhouse
     [not found]               ` <1118743045.20555.16.camel@server21>
     [not found]                 ` <20050614101107.GC2354@wohnheim.fh-wedel.de>
2005-06-15  2:25                   ` Munira Ahmed
2005-06-15  6:01                     ` Thomas Gleixner
2005-06-15  8:33                     ` Jörn Engel
2005-06-15  8:45                     ` David Woodhouse
2005-06-15  8:55                       ` Munira Ahmed
2005-06-15  9:02                         ` David Woodhouse
2005-06-15  9:04                           ` Munira Ahmed
     [not found] <8126E4F969BA254AB43EA03C59F44E840263CEAE@pdsmsx404>
2005-06-15  9:21 ` David Woodhouse
2005-06-16  5:38   ` zhao
2005-06-16  7:04     ` Artem B. Bityuckiy
2005-06-16  9:11       ` zhao
2005-06-16  9:28         ` Artem B. Bityuckiy
2005-06-16 10:24         ` David Woodhouse
2005-06-16 10:12     ` David Woodhouse
     [not found] <8126E4F969BA254AB43EA03C59F44E840263CED0@pdsmsx404>
2005-06-15 10:18 ` David Woodhouse
     [not found] <F760B14C9561B941B89469F59BA3A8470A558D56@orsmsx401.amr.corp.intel.com>
2005-06-16 18:06 ` 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=BAY7-F32F576C95CF56BEF0F5611DAF30@phx.gbl \
    --to=tongcd@hotmail.com \
    --cc=dedekind@yandex.ru \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=munira.ahmed@radixs.com \
    /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