From: David Woodhouse <dwmw2@infradead.org>
To: "Teuling, Sieme" <Sieme.Teuling@echostar.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: patch for nand support linux-2.4.21 jffs2?
Date: Tue, 18 May 2004 16:10:13 +0100 [thread overview]
Message-ID: <1084893013.28151.2.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <C86A9402F6A07E47B2F50A302DFA9BAE044C61@alm-exch.europe.echostar.com>
On Tue, 2004-05-18 at 08:59 -0600, Teuling, Sieme wrote:
> Ay!, I guess that means I'm looking at a fairly big merging effort, since
> using 2.4.26 is unfortunally not an option for me (we already ported 2.4.21
> to an embedded platform).
The changes from 2.4.21 to 2.4.26 should be relatively easy to merge.
Save yourself the heartache and just do it. As an added bonus you get a
kernel which isn't remotely exploitable.
> Do you guess merging the 2.4.26 mtd/jffs2 code into the 2.4.21 kernel is the
> (feasible) approach which most likely will take the least effort?, or is
> that likely just as much work as trying to merge the latest snapshot into
> the 2.4.21 kernel?
The only way you'll get it working is if you start backporting changes
in the core VFS code from 2.4.26.
Put 2.4.21 into CVS, update the CVS tree to 2.4.26 too. Now check out
2.4.21 and apply your own patches, having made sure there's no
gratuitous whitespace noise in your changes. Then CVS update and you
should find it's fairly easy to make it work.
--
dwmw2
next prev parent reply other threads:[~2004-05-18 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 14:59 patch for nand support linux-2.4.21 jffs2? Teuling, Sieme
2004-05-18 15:10 ` David Woodhouse [this message]
2004-05-19 9:55 ` Simon Haynes
2004-05-19 10:09 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-05-18 14:07 Teuling, Sieme
2004-05-18 14:28 ` David Woodhouse
2004-05-18 11:42 Teuling, Sieme
2004-05-18 12:31 ` 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=1084893013.28151.2.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=Sieme.Teuling@echostar.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