All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Chris AtLee <catlee@canada.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 on 2.2.18
Date: Mon, 10 Jun 2002 22:56:40 +0100	[thread overview]
Message-ID: <4337.1023746200@redhat.com> (raw)
In-Reply-To: <1023727479.20089.26.camel@geb>

catlee@canada.com said:
> I've had some success getting MTD and JFFS (v1) working on my 2.2.18
> system.  I've been trying over the past few weeks to get JFFS2 up and
> running.  I've got it to the point where the kernel can read a jffs2
> partition, but I really have no idea how to get writing to work.  The
> mechanism for writing seems completely different in 2.2.x than in
> 2.4.x

> Any pointers?  Is anyone else working on this? 

I know of nobody else working on a 2.2 backport. Worst case, you should be 
able to ditch the page-based write code and call jffs2_write_file_range() 
from a jffs2_file_write() which you provide instead of 
generic_file_write(), surely?

--
dwmw2

  reply	other threads:[~2002-06-10 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10 16:44 JFFS2 on 2.2.18 Chris AtLee
2002-06-10 21:56 ` David Woodhouse [this message]
2002-06-13 16:33   ` Chris AtLee

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=4337.1023746200@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=catlee@canada.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.