Re: MTD Config.in items not escaped by bus availability

Jörn Engel
2002-11-04T16:43:28Z

On Mon, 4 November 2002 09:29:51 -0500, Brian J. Murrell wrote:
>
> Of course, you are absolutely correct. I guess the reason I jumped
> the gun was that the last time I did this dance, there was no active
> maintainer so I went ahead and sent my patch to Marcelo my self. I
> guess I was just following the footsteps of my last time around with
> this sort of thing.
>
No problem. I've made bigger thinkos on a regular basis. :-(

> +++ linux-2.4.19-16mdkcustom.memory_bus/arch/alpha/defconfig 2002-11-01 18:50:35.000000000 -0500
> +++ linux-2.4.19-16mdkcustom.memory_bus/arch/i386/defconfig 2002-11-01 18:50:44.000000000 -0500
> +++ linux-2.4.19-16mdkcustom.memory_bus/arch/ia64/defconfig 2002-11-01 18:50:51.000000000 -0500
> +++ linux-2.4.19-16mdkcustom.memory_bus/arch/ppc/defconfig 2002-11-01 18:50:57.000000000 -0500
> +++ linux-2.4.19-16mdkcustom.memory_bus/arch/x86_64/defconfig 2002-11-01 18:51:03.000000000 -0500

That is five architectures out of of sixteen. You might argue that
s390 does not need mtd (which I'm not even sure about), but arm is
definitely missing and surely some more.

Can you add the other architectures or explain for each missing one,
why this was not necessary? Maybe I am just stupid.

Jörn

--
The cost of changing business rules is much more expensive for software
than for a secretaty.
-- unknown