From: Thomas Gleixner <tglx@linutronix.de>
To: 小明 <kevin@gv.com.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: can i use the cvs code directly in kernel 2.2.19 ?
Date: Wed, 21 Aug 2002 09:56:54 +0200 [thread overview]
Message-ID: <1029916619.1695.6.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <000b01c248de$37c21100$b30210ac@gv.com.tw>
On Wed, 2002-08-21 at 08:44, 小明 wrote:
> dear all,
> another question:
> can i use the cvs code directly in kernel 2.2.19 ?
> (currently it work fine with kernel 2.4.17)
Look for the inter_module patch in the patches/ directory of CVS.
It's for 2.2.17, but should apply to 2.2.19 too. There are some more
tweaks neccecary. There are 2 mailthreads (june, august 02) about that.
Citation dwmw2:
> 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().
BTW, did you test latest code in CVS ? Any problems left ?
--
Thomas
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2002-08-21 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 22:35 No free space left for GC Thomas Gleixner
2002-08-19 9:37 ` Massive file corruption Joakim Tjernlund
2002-08-19 21:47 ` No free space left for GC Thomas Gleixner
2002-08-19 22:34 ` Thomas Gleixner
2002-08-20 10:03 ` David Woodhouse
[not found] ` <015501c247f3$d13176a0$b30210ac@gv.com.tw>
2002-08-20 7:59 ` Thomas Gleixner
2002-08-20 15:47 ` Thomas Gleixner
2002-08-21 6:44 ` can i use the cvs code directly in kernel 2.2.19 ? 小明
2002-08-21 7:56 ` Thomas Gleixner [this message]
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=1029916619.1695.6.camel@thomas.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=kevin@gv.com.tw \
--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