From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Steve_Chen@kingston.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Porting JFFS II to 2.4.6
Date: Thu, 20 Dec 2001 12:01:06 +0100 [thread overview]
Message-ID: <20011220120106.A5941@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <OF26C7A171.C0609C8C-ON88256B26.007D0F13@LocalDomain>; from Steve_Chen@kingston.com on Wed, Dec 19, 2001 at 01:12:00PM -0800
Hi!
> I like to get some expert advice. We have frozen our development platform
> at kernel version 2.4.6 for months now. And we like to port the latest
> JFFS II source code from 2.4.16 to 2.4.6.
>
> I noticed that there are some structure changes in fs directory from 2.4.6
> to 2.4.16. What is the most effective way to do the porting ?
>
> 1) Do we just port the JFFS II code from 2.4.16 to 2.4.6 ??
Yup, do that and see, what all breaks. Then fix those parts and you
did it.
The best way would be to create a patch from 2.4.6 to 2.4.16 for the
jffs2 stuff exclusively, read it and see, what might/will break. You
might want to upgrade the mtd code as well, for obvious reasons.
Jörn
--
The next best thing to having good ideas is recognizing
good ideas from your users. Sometimes the latter is better.
prev parent reply other threads:[~2001-12-20 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 21:12 Porting JFFS II to 2.4.6 Steve_Chen
2001-12-20 11:01 ` Jörn Engel [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=20011220120106.A5941@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=Steve_Chen@kingston.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox