public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: mtd@infradead.org
Cc: trevw@zentropix.com
Subject: New release of MTD code pending.
Date: Mon, 27 Mar 2000 10:12:49 +0100	[thread overview]
Message-ID: <6013.954148369@devel2.axiom.internal> (raw)


I'm intending to make a new release some time this week.

I'd like to ship a tarball which holds drivers/mtd, along with two patches 
which add that directory to the kernel infrastructure.

I can't run 2.2 easily on my current testbed, so I would appreciate it if 
someone could give me a patch which adds _only_ the Makefile, arch/*/config.in 
and init code to the 2.2 kernel.

I'm going to update the FTL code so it compiles with 2.3 kernels - probably by 
taking David Hinds' latest version from the PCMCIA code and porting it to MTD 
again, so I get the last 3 years' worth of bug fixes while I'm at it.

The mtdblock driver needs fixing too - volunteers?

We're now in the interesting position of having two flash filesystems present 
in the tree - one of which (FFS2) compiles only on 2.2 kernels, and the other 
of which (JFFS) only compiles on 2.3. It'd be nice to fix that at some point.


--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~2000-03-27  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-27  9:12 David Woodhouse [this message]
2000-03-27 14:18 ` New release of MTD code pending Alexander Larsson
2000-03-27 14:24   ` David Woodhouse
2000-03-27 14:31     ` Alexander Larsson
2000-03-27 14:38       ` David Woodhouse
2000-03-27 14:55         ` Alexander Larsson
2000-03-27 15:22           ` David Woodhouse
2000-03-27 15:54     ` Trevor Woolven
     [not found] <Pine.LNX.3.96.1000327172759.26529E-100000@biffen.cendio.se>
2000-03-27 16:01 ` David Woodhouse

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=6013.954148369@devel2.axiom.internal \
    --to=dwmw2@infradead.org \
    --cc=mtd@infradead.org \
    --cc=trevw@zentropix.com \
    /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