public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jim Thompson <jim@musenki.com>
Cc: linux-mtd@lists.infradead.org, xkaspa06@fit.vutbr.cz
Subject: Re: patches to 2.4.18
Date: Fri, 03 May 2002 17:52:47 +0100	[thread overview]
Message-ID: <23173.1020444767@redhat.com> (raw)
In-Reply-To: <15570.48163.648146.185360@zaphod.musenki.com>

jim@musenki.com said:
>  Also, I (like so many others lately), had to comment out the call to
> invalidate_device() in mtdblock.c::mtdblock_release() in order to get
> my root filesystem (jffs2 on mtdblock on Intel Strataflash) to mount.

> I note that the call is still there in the CVS vsion:

Eep. That was removed from CVS long ago, but was added back again. I've now 
removed it again.

>  and we are getting crashes on halt/reboot if we've modified the
> filesystem. 

More details please.

>  Similar questions about jffs2 have been asked:
> 	http://mhonarc.axis.se/jffs-dev/msg01297.html
> With no apparent answer.
> anyone with clue to offer? 

For the MTD drivers, the code in 2.4.19-pre is probably the best option 
unless you need the new features I held back for 2.4.20-pre. For JFFS2, you 
should be using the code from the jffs2-2_4-branch in CVS. I _think_ that's 
all been sent to Marcelo for 2.4.19 though. 

--
dwmw2

  reply	other threads:[~2002-05-03 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 16:34 patches to 2.4.18 Jim Thompson
2002-05-03 16:52 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-07 18:10 John Sutton
2002-05-07 19:01 ` Thomas Gleixner

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=23173.1020444767@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jim@musenki.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=xkaspa06@fit.vutbr.cz \
    /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