Am Donnerstag, den 18.12.2014, 08:35 -0500 schrieb nick: > Krzysztof, > If we look at the code for this function, it already is handling the data > correctly. In addition the locks > seem to be better protection then msleep. Further more is no reason for this > delay as we are neither resetting > the hardware or waiting for the hardware here so why is it needed? I don't > have Exynos based hardware lying > around through to test it.
If you can't test it, don't touch it. It's that simple. Regards, Lucas -- Pengutronix e.K. | Lucas Stach | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
