On Fri, 22 Oct 2010, Maxim Levitsky wrote: > This reintroduces the bug I fixed. > > if the CONFIG_MMC_UNSAFE_RESUME isn't set (and that is default > unfortunately), the host->bus_ops->resume will be NULL (see core/mmc.c > mmc_ops), and therefore card will be removed, that will trigger a block > device removal, sync, and deadlock).
Maybe mmc_ops should have a non NULL resume method then? Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
