Hi folks, What is the function sdio_f0_readb() so special for? it seems to be used by a tiny handful of drivers and is equivalent to sdio_readb() with the function parameter set to 0. Its twin sdio_f0_writeb() does some very minimal checking for register bounds. Is it really worth all this abstraction for a few (usually wifi) drivers? surely the driver knows which registers it should touch anyway? its not like most bus drivers perform this sort of checking... Should this be done away with before more drivers start using it? I'm happy to submit a patch to remove sdio_f0*() -Ian -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
