From: Martin Michlmayr <tbm@cyrius.com>
To: akpm@osdl.org
Cc: linux-mips@linux-mips.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 8/12] [MTD] Re-add module description for ms02-nv to Kconfig
Date: Mon, 20 Mar 2006 04:40:26 +0000 [thread overview]
Message-ID: <20060320044026.GH20416@deprecation.cyrius.com> (raw)
In-Reply-To: <20060320043802.GA20389@deprecation.cyrius.com>
In an unrelated MTD commit, a description about the ms02-nv module
got removed from Kconfig. While I personally agree with this
removal, the module maintainer (Maciej W. Rozycki) would like to
see it added back. In the absense of any consistency regarding
Kconfig descriptions his wish should be followed.
Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
Acked-by: Maciej W. Rozycki <macro@linux-mips.org>
--- linux-2.6/drivers/mtd/devices/Kconfig 2006-03-05 19:35:04.000000000 +0000
+++ mips.git/drivers/mtd/devices/Kconfig 2006-03-05 18:51:15.000000000 +0000
@@ -47,6 +47,11 @@
accelerator. Say Y here if you have a DECstation 5000/2x0 or a
DECsystem 5900 equipped with such a module.
+ If you want to compile this driver as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt>. The module will
+ be called ms02-nv.o.
+
config MTD_DATAFLASH
tristate "Support for AT45xxx DataFlash"
depends on MTD && SPI_MASTER && EXPERIMENTAL
--
Martin Michlmayr
http://www.cyrius.com/
next parent reply other threads:[~2006-03-20 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060320043802.GA20389@deprecation.cyrius.com>
2006-03-20 4:40 ` Martin Michlmayr [this message]
2006-03-20 4:40 ` [PATCH 9/12] [MTD] Fix #else directive in the docprobe driver Martin Michlmayr
2006-03-20 4:40 ` [PATCH 10/12] [MTD] LASAT depends on MTD_CFI Martin Michlmayr
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=20060320044026.GH20416@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--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