From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: Dead mappings and drivers in MTD
Date: Mon, 11 Mar 2013 17:34:59 +0200 [thread overview]
Message-ID: <1363016099.3348.47.camel@sauron.fi.intel.com> (raw)
Hi MTD folks,
we have huge amount of drivers, espacially mapping drives in
'drivers/mtd', and for sure may of them are for ancient devices which
are long dead and not supported by modern kernels anyway. I would like
to do a small clean-up. It is difficult to judge which ones are dead for
me, so I am asking the community to help. Thanks!
There are few easy cases - some drivers depend on Kconfig symbols which
are not defined anywhere - I guess these are clear candidates for
removal. For example this one:
config MTD_DBOX2
tristate "CFI Flash device mapped on D-Box2"
depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
help
This enables access routines for the flash chips on the Nokia/Sagem
D-Box 2 board. If you have one of these boards and would like to use
Grepping for "DBOX2" gives nothing.
--
Best Regards,
Artem Bityutskiy
next reply other threads:[~2013-03-11 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 15:34 Artem Bityutskiy [this message]
2013-03-11 16:20 ` Dead mappings and drivers in MTD Olof Johansson
2013-03-11 16:43 ` 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=1363016099.3348.47.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).