From: ebiederman@lnxi.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: blkmtd and name_to_dev_t
Date: Mon, 03 Apr 2006 20:56:26 -0600 [thread overview]
Message-ID: <m3hd5anj51.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <442C6B78.3060706@zytor.com> (H. Peter Anvin's message of "Thu, 30 Mar 2006 15:36:24 -0800")
"H. Peter Anvin" <hpa@zytor.com> writes:
> There seems to be a few options, in order from least work to more work:
>
> - Removing the blkmtd driver and tell people to use block2mtd;
> - Have kinit intercept blkmtd configuration options and emulate them using
> block2mtd;
> - Adjust blkmtd to have a configuration interface, and then make kinit configure
> it.
Block devices are not especially interesting when working with flash chips, as they
are an emulation layer. The character devices are much more interesting,
and the native filesystems don't go through a block or a character device.
So killing blkmtd sounds like a reasonable thing to do.
Given that klibc will reduce the size of the kernel I expect most embedded
users will in general be in favor of it.
So I suggest what happens is that we deprecate blkmtd in Documentation/FeatureRemoval
of 2.6.17 and delete it in the -mm tree.
Then you can merge klibc.
Does any one have a problem with that plan?
Eric
next prev parent reply other threads:[~2006-04-04 2:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060329232520.1677d2b3.akpm@osdl.org>
[not found] ` <442C0494.2040609@zytor.com>
[not found] ` <20060330114014.53150d1b.akpm@osdl.org>
2006-03-30 23:36 ` blkmtd and name_to_dev_t H. Peter Anvin
2006-03-31 8:38 ` Jörn Engel
2006-03-31 15:10 ` H. Peter Anvin
2006-04-04 2:56 ` Eric W. Biederman [this message]
2006-04-04 3:07 ` H. Peter Anvin
2006-04-04 8:30 ` Jörn Engel
2006-04-04 8:42 ` Artem B. Bityutskiy
2006-04-04 8:46 ` Jörn Engel
2006-04-04 8:57 ` Artem B. Bityutskiy
2006-04-04 3:11 ` Josh Boyer
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=m3hd5anj51.fsf@maxwell.lnxi.com \
--to=ebiederman@lnxi.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--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