From: David Woodhouse <dwmw2@infradead.org>
To: jffs-dev@axis.com
Cc: mtd@infradead.org, linux@handhelds.org
Subject: JFFS in 2.2 - Call for testing.
Date: Fri, 04 Aug 2000 16:59:22 +0100 [thread overview]
Message-ID: <13576.965404762@cygnus.co.uk> (raw)
Ok. I've committed to my CVS the crap-but-safe fix to jffs_file_write() -
it kmalloc's a bounce buffer and copies the data into it, before passing it
to jffs_write_node().
Hopefully someone will do the 'proper' fix fairly soon - writes through the
page cache - but at the moment, I'm aware of no outstanding bugs in 2.2
JFFS.
I'm not sure I'd claim it's quite ready for production use, but it's getting
there. Suck it and see.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
reply other threads:[~2000-08-04 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=13576.965404762@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=jffs-dev@axis.com \
--cc=linux@handhelds.org \
--cc=mtd@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