Re: blkmtd and name_to_dev_t

["H. Peter Anvin" <hpa@zytor.com>]

Eric W. Biederman wrote:
> "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.
> 

I thought (am I wrong?) that blkmtd referred to using a block device as 
an MTD device.  Either which way, Jörn tells me that blkmtd is 
deprecated by block2mtd anyway, and only retained for boot support, 
which is pretty easy to do in klibc.

> 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?

That certainly works for me.  Jörn indicated he's going to sign off on a 
patch to remove blkmtd, which will solve my problem.

	-hpa