Re: MMC: Make the configuration memory resource optional

[Ian Molton]

Magnus Damm wrote:

> > Indeed.  It's actually much worse than you say, each individual ARM
> > architecture has its own clock API implementation of varying quality and
> > of course there are architectures that don't do the clock API at all.
>
> Yeah. This is exactly why I don't want to block on the clocklib implementation.

Yeah, good idea... lets ignore the problem until its so big we cant fix 
it at all...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/