From: Steven Scholz <steven.scholz@imc-berlin.de>
To: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: [RFD] Move 2.4 code out from CVS head
Date: Fri, 04 Mar 2005 08:31:02 +0100 [thread overview]
Message-ID: <42280EB6.4030007@imc-berlin.de> (raw)
In-Reply-To: <1109874008.29792.92.camel@baythorne.infradead.org>
David Woodhouse wrote:
> On Thu, 2005-03-03 at 11:48 -0500, Nicolas Pitre wrote:
>
>>>Does that mean that there will be _no_ " maintainence only mode" for
>>>2.4?
>>
>>Depends if _you_ or someone else decides to volunteer for the task.
>>do you? I don't.
>
>
> I _am_ maintaining JFFS2 in the 2.4 kernel, even to the extent of
> backporting the __wait_on_freeing_inode() stuff from 2.6 to fix the
> problems with simultaneous read_inode() and clear_inode(). But I'm not
> adding new features, so NAND flash isn't supported in 2.4.
How about SUMMARY patch then? ;-)
Seriously, since JFFS3 will not get into the 2.4 stuff Ferenc's SUMMARY patch
would be nice!
And BTW: How do I get the 2.4 branch from CVS?
--
Steven
next prev parent reply other threads:[~2005-03-04 7:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 9:14 [RFD] Move 2.4 code out from CVS head Thomas Gleixner
2005-03-03 10:28 ` David Woodhouse
2005-03-03 10:44 ` Thomas Gleixner
2005-03-03 10:46 ` David Woodhouse
2005-03-03 10:53 ` Thomas Gleixner
2005-03-03 11:00 ` David Woodhouse
2005-03-03 11:03 ` Thomas Gleixner
2005-03-03 11:05 ` David Woodhouse
2005-03-03 11:29 ` Steven Scholz
2005-03-03 11:38 ` Thomas Gleixner
2005-03-03 11:41 ` David Woodhouse
2005-03-03 16:48 ` Nicolas Pitre
2005-03-03 18:20 ` David Woodhouse
2005-03-04 7:31 ` Steven Scholz [this message]
2005-03-04 7:53 ` David Woodhouse
2005-03-04 9:00 ` Thomas Gleixner
2005-03-04 11:01 ` Artem B. Bityuckiy
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=42280EB6.4030007@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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.