From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Stefan Roese <sr@denx.de>,
linux-mtd@lists.infradead.org,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: [PATCH 1/5] MTD: make MTD_CONCAT support mandatory
Date: Tue, 11 Jan 2011 14:33:35 +0300 [thread overview]
Message-ID: <1294745619-7142-1-git-send-email-dbaryshkov@gmail.com> (raw)
Move mtdconcat to be an integral part of the mtd core. It's a tiny bit
of code, which bears 'say Y if you don't know what to do' note in the
Kconfig. OTOH there are several ugly ifdefs depending on the MTD_CONCAT.
So, making MTD_CONCAT support mandatory will allow us to clean up code a
lot.
Kconfig entry is changed to be a bool defaulting to Y, so all code
pieces depending on it, will have MTD_CONCAT Kconfig symbol and
CONFIG_MTD_CONCAT define. This will be removed in one of next patches.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Stefan Roese <sr@denx.de>
---
drivers/mtd/Kconfig | 3 ++-
drivers/mtd/Makefile | 3 +--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 1e2cbf5..38ca5f2 100644
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
@@ -34,7 +34,8 @@ config MTD_TESTS
various checks and verifications when loaded.
config MTD_CONCAT
- tristate "MTD concatenating support"
+ bool
+ default y
help
Support for concatenating several MTD devices into a single
(virtual) one. This allows you to have -for example- a JFFS(2)
diff --git a/drivers/mtd/Makefile b/drivers/mtd/Makefile
index 760abc5..a166b71 100644
--- a/drivers/mtd/Makefile
+++ b/drivers/mtd/Makefile
@@ -4,10 +4,9 @@
# Core functionality.
obj-$(CONFIG_MTD) += mtd.o
-mtd-y := mtdcore.o mtdsuper.o
+mtd-y := mtdcore.o mtdsuper.o mtdconcat.o
mtd-$(CONFIG_MTD_PARTITIONS) += mtdpart.o
-obj-$(CONFIG_MTD_CONCAT) += mtdconcat.o
obj-$(CONFIG_MTD_REDBOOT_PARTS) += redboot.o
obj-$(CONFIG_MTD_CMDLINE_PARTS) += cmdlinepart.o
obj-$(CONFIG_MTD_AFS_PARTS) += afs.o
--
1.7.2.3
next reply other threads:[~2011-01-11 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 11:33 Dmitry Eremin-Solenikov [this message]
2011-01-11 11:33 ` [PATCH 2/5] MTD: drop MTD_CONCAT dependencies from Kconfig Dmitry Eremin-Solenikov
2011-01-11 11:33 ` [PATCH 3/5] MTD: drop CONFIG_MTD_CONCAT ifdefs Dmitry Eremin-Solenikov
2011-01-11 11:33 ` [PATCH 4/5] CRIS: stop checking for MTD_CONCAT Dmitry Eremin-Solenikov
2011-01-12 12:40 ` Jesper Nilsson
2011-01-12 12:41 ` Dmitry Eremin-Solenikov
2011-01-18 11:05 ` Artem Bityutskiy
2011-01-18 14:58 ` Jesper Nilsson
2011-07-09 7:37 ` SV: " Mikael Starvik
2011-01-11 11:33 ` [PATCH 5/5] MTD: drop MTD_CONCAT from Kconfig entirely Dmitry Eremin-Solenikov
2011-01-12 13:25 ` [PATCH 1/5] MTD: make MTD_CONCAT support mandatory Stefan Roese
2011-02-15 14:07 ` Dmitry Eremin-Solenikov
2011-02-25 8:47 ` Artem Bityutskiy
2011-02-25 10:05 ` Dmitry Eremin-Solenikov
2011-02-25 10:15 ` Artem Bityutskiy
2011-02-25 10:35 ` Artem Bityutskiy
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=1294745619-7142-1-git-send-email-dbaryshkov@gmail.com \
--to=dbaryshkov@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sr@denx.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;
as well as URLs for NNTP newsgroup(s).