From: Thomas Eschenbacher <Thomas.Eschenbacher@gmx.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD in kernel 2.4.9
Date: Sat, 08 Sep 2001 12:52:10 +0200 [thread overview]
Message-ID: <3B99F85A.274309F0@gmx.de> (raw)
In-Reply-To: 20010906092901.A20085@kosh.hut.fi
Jarkko Lavinen wrote:
> [...]
> The complete_and_exit() problem I experienced was fixed in the 2.4.9 AC
> kernel by adding the wait queue head initialization just before forking the
> GC thread in jffs2_start_garbage_collect_thread(). That fixed the crashing
> GC thread problem in unmount.
>
> I haven't tried copying mtd CVS files over Linus kernels but on current
> AC kernels straight copying won't work. At least it will complain about
> missing up_and_exit().
It seems that Alan has fixed that in his patch-2.4.9-ac9.gz. JFFS2 now
compiles without complaining and even the entries in Configure.in and
the Makefile are present!
Thomas.
next prev parent reply other threads:[~2001-09-08 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 20:45 MTD in kernel 2.4.9 Thomas Eschenbacher
2001-09-05 22:21 ` David Woodhouse
2001-09-06 6:29 ` Jarkko Lavinen
2001-09-08 10:52 ` Thomas Eschenbacher [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 21:38 Vipin Malik
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=3B99F85A.274309F0@gmx.de \
--to=thomas.eschenbacher@gmx.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