From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Simon Evans <spse@secret.org.uk>,
"Eric W. Biederman" <ebiederman@lnxi.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: [Patch 2/3] Mark block2mtd as not deprecated
Date: Tue, 4 Apr 2006 11:29:30 +0200 [thread overview]
Message-ID: <20060404092930.GC12277@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20060404092628.GA12277@wohnheim.fh-wedel.de>
The last (and only) bugreport for this driver was > 1 year ago. There
is no reason to mark it as experimental anymore.
Signed-off-by: Jörn Engel <joern@wohnheim.fh-wedel.de>
---
drivers/mtd/devices/Kconfig | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--- blkmtd/drivers/mtd/devices/Kconfig~block2mtd_experimental 2006-04-04 11:05:33.000000000 +0200
+++ blkmtd/drivers/mtd/devices/Kconfig 2006-04-04 11:08:40.000000000 +0200
@@ -143,12 +143,10 @@ config MTD_BLKMTD
config MTD_BLOCK2MTD
tristate "MTD using block device (rewrite)"
- depends on MTD && EXPERIMENTAL
+ depends on MTD
help
This driver is basically the same at MTD_BLKMTD above, but
- experienced some interface changes plus serious speedups. In
- the long term, it should replace MTD_BLKMTD. Right now, you
- shouldn't entrust important data to it yet.
+ experienced some interface changes plus serious speedups.
comment "Disk-On-Chip Device Drivers"
next prev parent reply other threads:[~2006-04-04 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 9:26 [Patch 0/3] Remove blkmtd Jörn Engel
2006-04-04 9:28 ` [Patch 1/3] Immediatly deprecate blkmtd Jörn Engel
2006-04-04 12:08 ` Thomas Gleixner
2006-04-04 9:29 ` Jörn Engel [this message]
2006-04-04 11:18 ` [Patch 2/3] Mark block2mtd as not deprecated Jörn Engel
2006-04-04 12:09 ` Thomas Gleixner
2006-04-04 9:30 ` [Patch 3/3] Remove blkmtd Jörn Engel
2006-04-04 12:09 ` Thomas Gleixner
2006-04-05 6:47 ` [Patch 0/3] " Andrew Morton
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=20060404092930.GC12277@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=ebiederman@lnxi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=spse@secret.org.uk \
--cc=tglx@linutronix.de \
/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